Why do I have to regularly reconnect Slack to Airtable? It happens every few weeks or months, without warning (other than widespread automation-failed notifications). How can I avoid having to reconnect every automation that involves the ones I have set up to sent notifications via Slack?
Question
Frequently reconnecting Slack
+35
You may want to open a support ticket with support@airtable.com to see if they have some insights for you as to why this keeps happening.
Post back here with what they tell you!
In the meantime, if you’d like 100% reliable Slack automations that never need to be reconnected, and if you want Slack automations that give you significantly more power & significantly more customization than Airtable’s Slack automations, I highly recommend that you look into Make’s Slack automations alongside Make’s Airtable automations,
I have several Airtable consulting clients who have been using Make to automate Airtable with Slack FOR YEARS — I’m talking 5 or 6 years here — and they have never needed to reconnect their Slack connections in all these years.
If you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread.
For example, here is one of the many different ways that you can instantly trigger a Make automation from Airtable.
You can even instantly trigger a Make automation by having an interface button or URL link trigger a custom webhook (with optional webhook response).
I give live demonstrations of how to use Make in many of my Airtable podcast appearances. For example, in this video, I show how to work with Airtable arrays in Make. And in this video, I show how to use custom webhooks.
Hope this helps!
If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld
Most likely what is happening is a token expiry thing with your session on the Slack side rather than a bug with Airtable. Depending on the Slack workspace, it may have admin policies that force connected apps to frequently re-authenticate which is why you are noticing the few weeks or months pattern. Check whether your Slack workspace has an app session policy set by an admin and then whether the connection was made under a personal account vs. dedicated “bot” for automations. The dedicated service bots tend have a longer authorization because they are not tied to the individuals login.
In the meantime it might help to add a non-Slack fallback on your more critical automations like an email step. That way things will not fail silently and cause unknown chaos.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.