This topic was automatically generated from Slack. You can find the original thread here.
make give live : Is it possible to stack triggers in a workflow? I have 12 Airtable bases on a free account that I need to check every minute and update changes to a master Airtable table on a pro account.
I have simply duplicated my workflow 12 times and run it every minute but clearly I’m burning through my invocations :-(.
The changes may only occur every other day or sometimes once a week but I don’t ever know when or what time hence the need to run workflows constantly.
I wish I could trigger the workflows from a web hook but I don’t think it’s possible but maybe knows a way?
It’s for a social enterprise that make beanies on a buy one give one model www.makegivelive.co.nz
Chaim Krause : You can most definitely trigger from a webhook.
But first, can’t you turn it down to poling every 15, or 30, or 60 minutes. Do you really now immediately?
But an pipedream workflow can be triggered by a webhook. And, I do not know, but as sophisticated as Airtable is, I suspect they have an onChange or onSave webhook.
make give live : I know you can, it’s just that Airtable doesn’t have webhooks. They do have an on update trigger in Airtable but it only supports a few actions.
The free account doesn’t allow you to run scripts from automations only these actions:-
Send an email
• Create record
• Update record
• Send a Slack message
• Send a Microsoft Teams message
• Run a script (*Unavailable to customers on the free, Pro-trial or Creator plans)
• G Suite actions (Send email from Gmail account, Create new row in Google Sheet, Create a response to a Google Form, and Create a Google Calendar event)
Chaim Krause : Then, if you really wanna be a cheapskate than you have to work for it. Have airtable send a slack message and have a slack bot call your webhook.
make give live : $300 per month is too much for us as a social enterprise to have 15 collaborators on a pro account which is the number we need. If I could use Airtable’s own functionality I would. A slack message may be the way forward. Thank you for your contribution.
Dylan Sather (Pipedream) : have you seen the Slack event sources at Sources - Pipedream? I believe that might work for you if you’d like to rely on the Airtable -> Slack -> Pipedream integration to receive Airtable events. Each new message sent from Airtable should be emitted from your Slack source (behind the scenes, this happens via webhooks), and that can trigger any number of workflows
Chaim’s suggestion to reduce the frequence of the Airtable sources is also what I typically suggest if you’re trying to manage quota - even just reducing to once every 30 minutes can have a big impact.
make give live : Thanks . I’m familiar with your full implementation of Airtable slack pipedream but I wondered if the slack alert could trigger each of my existing workflows given that I know the relevant table ID from the slack message instead of running the full flow you created?
Chaim Krause : Sorry, I reread what I wrote
> Then, if you really wanna be a cheapskate than you have to work for it.
I meant that tongue in cheek. I can see now I forgot to add an emoji. What I meant is that it isn’t easy saving money.
Dylan Sather (Pipedream) : Can you direct all Slack notifications, for all 12 bases, to the same Airtable Slack channel? Or add the bot to 12 distinct channels such that all Slack notifications still hit your single workflow?
Dylan Sather (Pipedream) : btw what I meant earlier is that we’ve simplified the flow described in the Medium article, and added a Slack event source that’s triggered by new messages. That way you can avoid the bot setup:
Dylan Sather (Pipedream) : That event source would then trigger your workflow with the data from the message, which you can parse using similar code from the Medium article. Just a slightly simpler implementation
make give live : Hey Dylan - the connected slack app doesn’t seem to be receiving any messages, it’s just waiting for an event even though I think I’ve set it up correctly and messages are in slack
make give live : I thought it was due to my invocations expiring but I just upgraded to pro and it still persists - no mesages coming through to my workflow
