Workflow Buddy - Super powers for Workflow Builder

| 📂 Open-source | 🧪 Installable App | 💡 Support |

☠️ Slack Killing Capability

Unfortunately, Slack has decided they will be deprecating the Steps from Apps feature, which is what powers Workflow Buddy. That will happen on Sept 12, 2024. We will continue supporting the application until Slack turns off support, as well as looking at ways to use their new platform. More info here, and a blog post from the Workflow Steps for Jira team with how they are handling it.

Testimonials

🗣 "Workflow Buddy is such an enabler for us. It’s exactly what I hoped Workflow Builder originally was." - iCulture.nl

🗣 "It’s like a mini Zapier in Slack… By using Buddy I was able to remove many unnecessary formatting steps from Zapier, effectively saving me money." - Feedback during Alpha

Workflow Builder is great!

... and it has great potential, too! 😅

The current implementation you get out of the box is a bit boxed in by:

a small selection of built-in Slack triggers (5).
- shortcut, new channel member, emoji reaction, schedule, webhook
a VERY limited selection of built-in Slack actions (2) - To give them credit, this has increased with the Spring 2023 Workflow Builder release - Slack's available functions
- send a message, send a form

You can get creative and do a lot with these building blocks, but what if you want to do more?

🥳 ✨ Ta-da! ✨

This Slack App acts as an extension of Workflow Builder, providing access to significantly more Slack triggers (such as app_mention, channel_created, etc.) and expanding the suite of Steps available.

⚡ The most important Step this app adds is the Outgoing Webhook/HTTP Request, which enables users to integrate their Slack Workflow Steps with almost any other application.

About
- Demo Videos
- Available Event Triggers - +Many
- Available Steps - +15
- Improving UX for Slack Workflows
- Common Use Cases
Quick Starts - 🎉 test me out! 🧪
- (Beginner) Simple Workflow - (~10 mins)
- (Advanced) Try New Event Triggers - (~25 mins)
- (Advanced) Try New Steps - (~25 mins)
Self-hosting - (45-75 mins)
Example Workflow Templates
FAQ
Support

Support

Want to get rockin' with Workflow Buddy, but running into trouble? You have a number of resources to help you out:

📚 Read the docs - in this README, and the wiki
👬 Search through or ask a question in the Community Discussions - no question is too small.
📩 Send an email to support@happybara.io.
🙋‍♀️ If you found a bug; open a new GitHub issue. ⚠ If in doubt, please use the Discussions rather than Issues.

Demos

Hate reading and would rather see videos of it in action?

A ~3min video demo showing a custom event triggering a Workflow which runs the majority of the available Step actions.
A ~3min video demo showing how to go from downloaded template to triggering a Workflow that sends an Outgoing Webhook, along with a bonus of showing how to proxy slack events to another service.

Example Workflows

See the test_workflows/ folder for example Workflow templates you can use either as a base for your own, or to see what is possible with Workflow Buddy.

single_webhook_test.slackworkflow
- This example has a single step showing how one can send an Webhook/HTTP Request to the test site webhook.site.
http_testing.slackworkflow - This example showcases some more creative uses of response from the Webhook/HTTP Request, using the JSON Extractor step multiple times to parse data and make it available as Slack Workflow Variables later in your pipeline.
workflow_buddy_end_to_end_test_read_only.slackworkflow - The kitchen sink, almost. Has almost all of the available utilities, including extra features like Debug.

⛏ Use Cases

What can you do with these extra triggers and actions?

Trigger Slack Workflows with (almost) any event

Expand beyond the limited number of events that Workflow Builder comes with out of the box.

Replace the legacy Outgoing Webhooks

Slack used to offer Outgoing Webhooks as a way to listen for new messages/Trigger Words in Slack messages and then fire a webhook to external URLs.

It has a warning at the top though "Please note, this is a legacy custom integration - an outdated way for teams to integrate with Slack. These integrations lack newer features and they will be deprecated and possibly removed in the future.". To avoid any issues, you can alternatively use WorkflowBuddy to accomplish the same thing (in 2 ways!).

Enable listening for message* events, then either directly proxy the event to your webhook (by adding it to the Event-Webhook Map in App Home) or use the Step: Send a Webhook/HTTP Request as part of a longer Workflow.

* WorkflowBuddy doesn't yet have the same granularity for filtering events, but it is on the potential roadmap.

Reuse the same Workflow for multiple channels across a Workspace

Slack Workflows are currently tied to a single channel, which can be a hold up if you want to track events across multiple. To stick within Workflow Builder, you need to download and duplicate the same workflow for every possible channel you want..... or just use Workflow Buddy and proxy all the events to a single Workflow.

Example for reaction added:

Invite Workflow Buddy to each of the channels you want it to listen for reactions in.
Set up your desired Workflow as a Webhook-triggered in Workflow Builder. Publish and copy the URL.
In the Workflow Buddy App Home, configure the reaction_added event with the Webhook from previous step.
🧪 Test by reacting to some messages! Any channel the bot has been invited to will send their events through Workflow Buddy - and onward to your Workflow.

Start other Worflows from the middle of a Workflow

With the power of webhooks, you can use actions and outcomes in the middle of a Workflow to start other Slack Workflows or automation in other tools. E.g. send a receipt to a customer while you're in the middle of processing the Workflow.

Have as many events as you want trigger a Workflow

With Slack Workflow Builder, you can only configure a single event to trigger your Workflow (e.g. _person added to a specific channel). Workflow Buddy has no restrictions on the number or variety of event->webhook mappings you configure. Maybe you want all the channel_* event types to kick off a workflow, or you want to have incoming events sent in parallel to a Webhook testing site while you're debugging your workflow.

⚠: "Webhook workflows are limited to one request per second."-src. You can enable numerous events, but you also can't hammer the service with 50K workflow executions, so be careful when using the high-volume events like message.

Send data from Slack Workflow to other apps

Use the customizable Outgoing Webhook Step as part of a workflow and fill the JSON body with relevant context. Examples might be triggering Airtable automations when your Workflow is finished, or kicking off GitHub Actions.

Proxy Slack events to another service

Workflow Buddy was originally intended for expanding the available Workflow Builder triggers within Slack, but it can also be used to proxy Slack events to another service - bypassing Workflow Builder entirely. This can be done by following parts of the New Event Triggers Guide. You can skip creating a workflow, then after double checking your OAuth scopes are all set, you can Add a new event-> webhook mapping and connect the event to your external services URL.

ℹ️: When using in this advanced manner, you'll want to set your webhook configuration setting raw_event: true. See Raw Event in Options.

Your great idea here

There are tons of awesome use cases we haven't thought of yet, submit a PR or reach out to tell us about yours! You can also find more general templates at Workflow Builder Templates | Building on Slack.

🏁🎬 Available Triggers

All* Slack events proxied through to any webhook-triggered Workflows.** See "Templates to save time" for copyable webhook starting points.

*During alpha stage, only a small number of events have been implemented, but goal is to quickly update to handle 80-90% of uses cases, and eventually 100%. ** While WorkflowBuddy code will work out of the box as an event proxy, you will need to update your app's OAuth scopes & event subscriptions for your new events, as well as save the webhook event from your Workflow in the config.

Events

The events that have been tested and are known to be working - other Slack events should work, but have not had the same testing done.

Options is the keys you can add to the Webhook config options through App Home. If the option isn't visible in Add modal, then it can be added directly by:

Export the config.
Edit it to add your desired Options.
Import the updated config.

Global Options

Options that work the same across event types.

use_raw_event: By default, Workflow Buddy will flatten & limit the JSON it receives to fit with the Slack limitations of 20 variables and no nested data. Set this to true to turn off the transformation.

app_mention - docs

happy path tested
template: event_trigger_example_workflows/trigger_app_mention.slackworkflow.

Listen for when your bot gets mentioned across the workspace.

Options:

filter_channel - Channel ID. If you want to filter down to a single channel. Example use case: Workflow triggered by mentioning bot in a specific channel.

channel_created - docs

happy path tested
template: event_trigger_example_workflows/trigger_channel_created.slackworkflow.

Listen for new channels being created.

reaction_added - docs

happy path tested
template: event_trigger_example_workflows/trigger_reaction_added.slackworkflow.

If you only want a single reaction type (e.g. 😀) in a single channel, then you'll want to just use the Workflow Builder built-in. The Workflow Buddy version provides a bit more functionality.

Listen to All reactions coming in - not just a single.
Listen across every conversation Workflow Buddy is apart of - not just a single channel. Tested in public & private channels.

Options:

filter_react - the emoji/reaction you want to let through.
filter_channel - Channel ID. If you want to filter down to a single channel. Example use case: Workflow triggered by any emoji reaction in a specific channel.

Templates for Event Triggers

When using Workflow Builder Webhooks, it requires allow-listing any data keys you want to use from the request body. To make this easier, in event_trigger_example_workflows/, you can find templates that already have all the requisite keys already in place, matching the core payload from the Slack API.

⚠️Limitations

Slack restrictions

Max of 20 variables allowed.

Cannot handle nested JSON.

Workflow fails if all variables not present.

Workflow Buddy

Only a small number of templates have been completed so far, good contribution opportunity!

Currently the wrapping payload is not included, but it could be an easy contribution in the future.

🏃 Available Steps

The utilities currently available within WorkflowBuddy for use as Workflow Steps. To see the exact inputs & outputs without loading up Workflow Builder, see constants.py.

Send an Outgoing Webhook/ HTTP Request

Send data from your Slack Workflows to almost any service. You can trigger GitHub repos, Jenkins Builds, Salesforce actions, you name it. Read a bit more about the use cases on the site HTTP Request Tool | Building on Slack.

Extract Values from JSON

Use JSONPATH expressions to extract data from JSON strings in your Workflows to use as variable in other Steps. Common use case is to parse a value out of an HTTP response body.

Need multiple values? For now, you can just use this Step multiple times in a Workflow for each value you need. In the future, we plan to support multiple in one Step.

Wait for human | approval | manual completion

Many names to describe it. In short, have your workflow wait in an In progress state until a human has taken action to either Complete➡ and let the Workflow continue, or Fail❌ it and stop the flow.

Wait for Webhook/ HTTP Request

Have your workflow wait in an In progress state until it receives a webhook from an external service. You can choose to either Complete➡ and let the Workflow continue, or Fail❌ it and stop the flow.

Example body Workflow Buddy expects:

{
  "execution_id": "4364223353762.667214953526.b8f41739087702effd5ac3b0b514006f",
  "sk": "RTPLSJVIBcmCAUcnUtbI",
  "mark_as_failed": true,
  "err_msg": "My sevice blew up!"
}

How do you get the execution ID? When saving the step, you will define a URL for Workflow Buddy to send the required data to. You could also get it from the Manual Complete step if it better fits your use case.

Wait/ Pause / Delay (seconds)

Have your workflow wait for up to 60s. After this was developed, Slack released a Delay option in minutes - this lets you get more granular, as is sometimes required.

Random Integer

Generate a random integer in the range [lower_bound-upper_bound], inclusive.

Example: Given 5 - 15, would output random value like 11.

Random UUID

Generate a random UUID with Python's standard library.

Example: a3b45ac2-d1ba-4c54-9e1c-0d51983ec952.

(Slack) Random Member Picker

Core API Method

Choose a random sample of 1+ non-bot users from a conversation. Each user is available as an individual variable in future Workflow Steps.

(Slack) Create a channel

Core API Method

This action will create a new channel with your specified name, then return the channel_id as both text & the channel type so it can be used in Slack's built-in functions.

(Slack) Find user by email

Core API Method

Get a user based on their Slack email. Returns the user as both a text user_id and a user type so it can be used in Slack's built-in functions.

(Slack) Get Email From User ID

Get email based on a Slack user ID. Useful when you have plain text user IDs in your Workflow.

⚠ If your variable is a 'user' type, you already have access to the email and don't need to use this utility! To access, insert the variable into your input, then click on it - from there you can choose from mention <@U1234>, name First Last, or email you@example.com.

(Slack) Schedule a message

Core API Method
Advanced formatting in Slack messages Schedule bot messages to public channels up to 120 days in the future.

(Slack) Set Channel Topic

Core API Method

Set the topic for any conversation that Workflow Buddy has been invited to.

(Slack) Add Reaction

Core API Method

Adds a reaction to a message, given the permalink URL. Works with the Slack built-in Reaction Added Workflow Trigger.

(Slack) Find a Message

Core API Method

Query the Slack search and return the top result as Workflow variables.

⚠ The Slack search endpoint requires a User token, which will be based on whoever installed the Workflow Buddy app. Results will be constrained to what that user is able to search. If you are running into issues with the user token, please Open an Issue 🐛.

More to come

See Issue #10 for discussion on potential Step actions to add.

Bonus Utilities/ UX Improvements

Occasionally I run into handy utilities that make life easier when building automations for Slack workspaces, and what better place than a toolkit like Workflow Buddy!

Debug Mode

For any Workflow Buddy Step, you can enable Debug Mode, which will pause and send you a message with information about the inputs and metadata, then wait for you to click Continue.

Learn More | Wiki

Error Notifications

Slack Workflows don't have an obvious way to notify for failures in your Workflows - you have to keep checking back to find out if things haven't been working. For Workflow Buddy Steps, there is an option to configure a notification conversation so any time errors happen, it will ping you rather than making you check.

ℹ️ Unfortunately, this only works for Workflow Buddy Steps, not all Steps in your workflow. Unfortunately we don't have a way to intercept other applications failures.

Shortcut: Inspect Message

A message shortcut that pulls up the associated metadata Slack has for it, including useful attributes like team_id, user_id, message ts, etc. Handy when being a Builder of Workflows or developing steps.

🏁 Quickstarts

Follow a walk-through to get a feel for what the system can do.

Beginner Quickstart: Create a Simple Workflow

Let's open up Workflow Builder and put together a simple Workflow that starts from a Slack Shortcut, uses some of the simple utilities that Workflow Buddy provides, then sends you a message with the output.

⚠ If you don't already have a channel for testing purposes, go create one. We don't want to annoy any of your team mates with random messages.

ℹ If you haven't yet, you'll need to get a Buddy instance running + a Slack app. Come back when you're ready.

Open up Workflow Builder (Top left Workspace menu -> Tools -> Workflow Builder)
Click Create.
Give it a name, like workflow buddy test.
Select Shortcut from the Trigger options.
Select your testing channel as the location. Add the short name.

🙌 Awesome! You just built a minimal no-op (do nothing) workflow. Let's make it do something more fun!

Add Step 1
- Click Add Step. You should see a couple Workflow Buddy actions available along with other Steps available in your workspace.
- choose Utilities from Workflow Buddy. Then once the modal appears, change the drop down to Random UUID.
- Save!
Add Step 2
- Click Add Step again.
- Choose Send a message. In the modal, choose Person who clicked... as the recipient. In the Message text section, try Insert a variable and choose Random UUID from the dropdown to add it to your message text. Feel free to add any other sentences you want alongside the UUID variable.
  What did we just do?
  - Slack lets you access the outputs of previous steps as Variables. Next to any text input box you will see that Insert a variable option. Sometimes it even lets you use them in drop downs, like when you selected the Person who clicked.. - that's a variable representing anyone who clicks the workflow!
  - The majority of Workflow Buddy actions will provide Outputs that you can use in future Steps - webhook response codes, random numbers, Slack users, etc. Try and get creative - sending a message with the info is only the beginning of possibilities. How might you link multiple actions together with variables?
- Save!
Click Publish.

🧪 The Workflow is now ready for testing! Go to your test channel you added the Workflow to, open up the Shortcuts menu, and you should see your Short name you chose in the options. Click it!

If everything was correct, you should receive a message with a random UUID value and the text you wrote!

✅You successfully created a Slack Workflow using Steps from both Workflow Buddy and Slack, awesome!

If you are looking to explore more advanced concepts like Triggers or advanced Workflow Buddy Steps, check out the Advanced Quickstarts below. Otherwise feel free to keep poking around on your own in Workflow Builder. There's endless possibilities, so automate everything!

Advanced Quickstart: Run New Steps

Try out the new Steps by importing a Workflow that has ~~all~~ most of them configured (except for ones that make changes to your Slack Workspace, like Create a channel. Don't want to cause any weird side-effects during your testing!).

ℹ If you haven't yet, you'll need to get a Buddy instance running + a Slack app or install the Cloud version. Come back when you're ready.

Download the Workflow template from test_workflows/workflow_buddy_end_to_end_test_read_only.slackworkflow(link), which contains all the basic functionality of Workflow Buddy Steps.
Open Workflow Builder, Import, and Publish it!
Click the Edit button on each of the configured Steps in the Workflow so you can see how each available action is configured. Several require updates:
- Invite your new @WorkflowBuddy app to the channel you attached the Workflow Shortcut to - otherwise, the setTopic action will fail.
- (Optional) From the @WorkflowBuddy App Home, add a notification channel for failures - that way, if anything goes wrong during setup, you'll find out! Sadly, by default Slack's Workflow Builder will fail silently.
- In Schedule message, you'll likely need to update the timestamp.
🏃‍♂️Run the Workflow!
- If you decided not to add failure notifications, or you haven't seen anything happening for ~3 mins, check in Workflow Builder's Activity tab to ensure that your execution is in progress - it might be waiting for you to respond to a message!

✅ That's it!

You now have the abiltity to use all of the Workflow Buddy Steps for your Workflows now!

Go forth and automate!

Advanced Quickstart: New Event Triggers

We're gonna start with a simple event we can easily control: app_mention (when your bot is @WorkflowBuddy in a channel). We will use that event to kick off a simple Workflow that just sends us a message.