Slack messages can contain interactive elements like buttons, dropdowns, radio buttons, and more. This source subscribes to interactive events, like when a button is clicked in a message.
Then this source will be triggered when you or another Slack user in your workspace clicks a button, selects an option or fills out a form.
With this trigger, you can build workflows that perform some work with other APIs or services, and then reply back to the original message.
What this short video to learn how to use this in a workflow, or follow the guide below.
First, if you haven’t already - send yourself a message containing one or more interactive elements. Use the Sending the message with an interactive element guide below to send a messsage containing a button.
If you have already sent a message containing an element, skip to Configuring the source.
Sending the message with an interactive element
The easiest way is to send yourself a message using the Slack - Send Message Using Block Kit action:
)
Then select a Channel you’d like to send the message to, and use the Block Kit Builder to build a message, or just copy the example button blocks below:
Your Slack - Send Message Using Block Kit should look like this:
Configuring the source
By default, this source will listen to all interactive events from your Slack workspace that your connected Slack account has authorization to view.
You can filter these events by selecting a specific channel and/or a specific action_id.
Filtering interactive events by channel
Use the Channels dropdown to search for a specific channel for this source to subscribe to. Only button clicks, dropdown selects, etc. in this selected channel will trigger the source.
Filtering interactive events by action_id
For more specificity, you can filter based on the passed action_id to the message.
The action_id is arbitrary. It’s defined on the initial message sending the button, dropdown, or other interactive element’s markup.
For example, in the section above using the Block Kit to create a message, we defined the button’s action_id as "button_click". But you can choose whichever naming convention you’d like.
If you pass button_click as a required action_id to this source, then only interactivity events with the action_id of "button_click" will trigger this source.
▶
Watch us build a workflow
7 min
Watch now ➜
Trusted by 500,000+ developers from startups to Fortune 500 companies
This is a pre-built, source-available component from Pipedream's GitHub repo. The component is developed by Pipedream and the community, and verified and maintained by Pipedream.
To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.
New Interaction Events on Slack
Description:Emit new events on new Slack [interactivity events](https://api.slack.com/interactivity) sourced from [Block Kit interactive elements](https://api.slack.com/interactivity/components), [Slash commands](https://api.slack.com/interactivity/slash-commands), or [Shortcuts](https://api.slack.com/interactivity/shortcuts).
import common from"../common/base.mjs";exportdefault{name:"New Interaction Events",version:"0.0.9",key:"slack-new-interaction-event-received",description:"Emit new events on new Slack [interactivity events](https://api.slack.com/interactivity) sourced from [Block Kit interactive elements](https://api.slack.com/interactivity/components), [Slash commands](https://api.slack.com/interactivity/slash-commands), or [Shortcuts](https://api.slack.com/interactivity/shortcuts).",type:"source",props:{...common.props,action_ids:{type:"string[]",label:"Action IDs",description:"Filter interaction events by specific `action_id`'s to subscribe for new interaction events. If none selected, all `action_ids` will emit new events.",optional:true,default:[],},conversations:{propDefinition:[
common.props.slack,"conversation",],type:"string[]",label:"Channels",description:"Filter interaction events by one or more channels. If none selected, any interaction event in any channel will emit new events.",optional:true,default:[],},// eslint-disable-next-line pipedream/props-description,pipedream/props-labelslackApphook:{type:"$.interface.apphook",appProp:"slack",/**
* Subscribes to potentially 4 different events:
* `interaction_events` - all interaction events on the authenticated account
* `interaction_events:${action_id}` - all interaction events with a specific given action_id
* `interaction_events:${channel_id}` - all interaction events within a specific channel
* `interaction_events:${channel_id}:${action_id}` - action_id within a specific channel
* @returns string[]
*/asynceventNames(){// start with action_ids, since they can be the most specificconst action_events =this.action_ids.reduce((carry, action_id)=>{// if channels are provided, spread themif(this.conversations &&this.conversations.length >0){return[...carry,...this.conversations.map((channel)=>`interaction_events:${channel}:${action_id}`,),];}return[...carry,`interaction_events:${action_id}`,];},[]);if(action_events.length >0)return action_events;// if no action_ids are specified, move down to channelsconst channel_events =this.conversations.map((channel)=>`interaction_events:${channel}`,);if(channel_events.length >0)return channel_events;// if not specific action_ids or channels are specified, subscribe to all eventsreturn["interaction_events",];},},},methods:{},asyncrun(event){this.$emit({
event,},{summary:`New interaction event${
event?.channel?.id
?` in channel ${event.channel.id}`:""}${
event.actions?.length >0?` from action_ids ${event.actions
.map((action)=> action.action_id).join(", ")}`:""}`,ts: Date.now(),},);},};
Slack uses OAuth authentication. When you connect your Slack account, Pipedream will open a popup window where you can sign into Slack and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Slack API.
Pipedream requests the following authorization scopes when you connect your account:
Slack is a channel-based messaging platform. With Slack, people can work together more effectively, connect all their software tools and services, and find the information they need to do their best work — all within a secure, enterprise-grade environment.
)
Chase Roberts@chsrbrts@benedictevans If you haven’t used @pipedream yet, then you haven’t lived.
✨Ellie Day✨@heyelliedayEvaluation update: @pipedream has quite literally been a dream to work with! I’m excited to leverage this tool for all the various workflows I need to write. I’m currently at 11k invocations a day from the initial workflows I’ve written in the past couple weeks.
Michael Braedley@MBraedleyUpdate: I got it working properly, and it's working so well that I'm dropping IFTTT. @pipedream can do everything that IFTTT basic can, and most (if not all things) IFTTT pro can for free or at a reasonable price if you need it. I am recommending it for basically any power user.
Thomas Cutting@mrthomascuttingWant quick+dirty integrations for a serverless workflow - @pipedream is my new go-to 😃
Matthew Roberts@mattdotrobertsday 013 - finally hit node js. This is the secret sauce of taking #nocode projects that one step further. Pumped about getting deeper into @pipedream now
Kenneth Auchenberg 💭@auchenbergYahoo Pipes is back! Kinda 😍 @pipedream
Raymond Camden 🥑@raymondcamdenAwesome video by the @pipedream folks showing real time twitter sentiment analysis integrated with Google Sheets. This is where Pipedream *really* shines, connecting systems together in easy workflows.
Nacho Caballero@nachocaballeroI couldn't recommend @pipedream more. It's an amazing service to integrate different APIs. Much more powerful than Zapier and more user-friendly than AWS Lambda. I'm very proud to wear this t-shirt #NoCode
Jason Snow@jyksnwDeveloped a working prototype environmental sensor IoT solution with @particle Photon, @pipedream, and @MongoDB with full graphing and alerting in less than a day! All amazing technology, will def. be exploring these more.
Steven Terrana@steven_terrana@burgwyn you've inspired me to finally set up my own blog. I'll make sure my first blog post explains the tech behind the setup. think @obsdmd + @GatsbyJS + @pipedream.
🚄 James Augeri, PhD@DotDotJamesWant to low-code your back end, need more horsepower than @Bubble / @KnackHQ, or just miss Yahoo! Pipes? Check out @PipeDream
Sébastien Chopin@AtinuxGitHub issues should be like @linear_app for maintainers. Looking forward more integrations with GH actions or tools like @pipedream 👀
Raul@raul_predescuIf you're a dev and not using @pipedream, you're missing out. Been using it for months, daily. FREE for devs. Plenty of integrations and good limits. Absolutely love it.
Bruno Skvorc@bitfallsSo @pipedream is pretty amazing. In 3 minutes I just made a flow which adds @rickastley's Never Gonna Give You Up to my @spotify playlist whenever a new pull request arrives in an old repo of mine.
Zach Lanich@ZachLanichUm, wow 🤯 @pipedream
Steven Bell@bellontechI just used @pipedream to build a Shopify App. Wow, they make small backed tasks easy.
Jay Hack 🎩🇺🇸@_jayhack_Very impressed with this bad boi - it reminds me of a @PalantirTech internal tool, but geared towards integrations instead of data analysis and far more customizable. Great expectations here 🚀🤩
Tree Sturgeon 🔥🚴♂️🌳@philsturgeonFor context this is day 2 of a really challenging and stupid migration from Notion to @airtable with disparate/missing data. It's going better than expected and thanks to @pipedream I don't have to bother the iOS dev to add W3W.