I don't know about you but this takes up a TON of my time. But then you update Zapier and boom, this is out-of-sync and then your job turns into documenting and updating that information versus just building solid zaps. To share with clients or just for internal documentation. So then we start storing this information in external tools like Airtable and Coda, building out things like this (will upload pic later): It is not easily skimmable/referenceable. Then there is the native " Add a note" option within the zap, but it is so hidden and out of the way, and I have typed up essays in there before and forgotten to "save" enough times to get frustrated to not use it much anymore.Īt the end of the day, it is out of sight, out of mind. Lookup Project Lead Name For Email Addressīut it gets truncated after the first 3-4 words so it's impossible to easily skim. I try to label each trigger/action title with what it is doing. Then there is actually jumping into the zap. Naming it like I have above is not very easy on the eyes and it is starting to get a bit overwhelming. Zapier only shows the Trigger + # + Final Action which isn't very helpful for a 4+ step zap. There is a lot going on above, but I can skim a zap and have a pretty good idea of what is going on. ![]() I have been using this type of structure for a while for the naming scheme of a zap:ĬLIENT - (2|5) (Opportunity - Project) Active Job Stage > Find/Create Customer > Create Invoice > Lookup Project Lead Name For Email Address > Create Activity > Da (TRUNCATED - TOO LONG OF TITLE) There's currently no easy or standardized way to document the more complex Zaps. If you're experiencing persistent issues or have specific questions about the deprecation, consider reaching out to Zapier's support for assistance.Īlways refer to the most recent documentation and support resources for both Zapier and Airtable to ensure you have the latest and most accurate information.Trying to repurpose a comment that I posted on the prior community forum that involves this same question:.This helps catch any potential issues early on. After updating each zap, thoroughly test it to ensure it functions as expected with the new Airtable connection.Copying a zap allows you to replicate its settings, and you can then modify the necessary details for the new Airtable connection. To streamline this process, consider using the "Copy Zap" feature.You might need to update them one by one. Unfortunately, there isn't a direct "batch update" feature in Zapier for updating multiple zaps simultaneously.This ensures you're using the latest integration and avoids potential issues with deprecated features. If the current Airtable connection is deprecated, you may need to create new zaps with a fresh connection to Airtable. ![]() This can provide insights into any deprecations or changes in the integration. ![]() Review the Zapier updates and announcements to see if there are any changes or updates related to the Airtable integration.Here's a general approach you can consider: He "Deprecated" status for Airtable could indicate that the current connection method or version might no longer be supported or recommended.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |