The only logic Zapier knows are the "Only continue if" filters as described in the first Zap. If idToTweetNext = 5 then idToTweetNext = 1 else idToTweetNext = idToTweetNext + 1 Unfortunately, Zapier cannot do real conditional logic. I need to create some logic to tell it: "6 is out of bounds, go back to 1". When the 5th Tweet is posted, "idToTweetNext" will be updated to 6.
Let's assume I have 5 tweets in my database.
ZAPIER AIRTABLE FILTER UPDATE
I also update the "LastPosted" date, which is not used by the logic, but might be useful for troubleshooting. When the Tweet is posted, I can increment the "idToTweetNext" variable so that it points to the next Tweet in line. With this ID in hand, it is straightforward to query Airtable and get the correct Tweet. To know which Tweet to post, I saved an index in a variable and update it manually. I implemented this version with 3 different "Zaps" (Zapier workflows).Īt the end, this Zap increments a variable containing the number of Tweets saved. When we reach the end of the list, we cycle back to ID #1. Thus, have a table that is sorted per ID and I "just" need to keep count of which ID was retweeted last. The next idea is to add an ID to all the Tweets that are saved and always insert the new tweets at the end. Unfortunately, this has been a feature request since. You need to manually apply the sorting again. You can add a default sorting to a table but if you add an element, the sorting is not "re-applied" automatically. Unfortunately, Airtable has an annoying limitation: it doesn't automatically apply table sorting. Update the saved date of the retweeted Tweet to today.Upon initial saving of the Tweet, save the date.The first started with the simplest idea I had: Like the Know Your Company use case, I used Airtable as a Database and Zapier to create the workflow. When it has gone through the whole list, start again at the top.At regular interval (daily), retweet one of them.Save every of my own Tweet that matches a given query, in this case all my mentoring-related Tweets.
Here are the scenarios it should fulfill: Here's another unconventional use case built with Airtable and Zapier: a retweet scheduler.
0 kommentar(er)
