![]() ![]() If I don't touch it, it will continue re-tweeting my best tweets and bug by followers with the same ideas forever. If I save a Tweet that is longer than this, I should send a notification to manually edit modify the Tweet. Thus, I need to make sure that my Tweets are not longer than 277 characters. I add the 3 characters "Re:" at the beginning of the Tweets. And that's why I saved the number of tweets in the first Zap. So, I compute this modulo in a first step, and then only continue to reset it to 1 if the result was 0. Only continue if the remainder of the division of "idToTweetNext" and "numberOfTweetsSaved" is 0, and then reset "idToTweetNext" to 1 The right-hand side of an operation can only be a static value. Only continue if "idToTweetNext" > "numberOfTweetsSaved" and then reset "idToTweetNext" to 1.įurther problem, Zapier filters cannot compare two dynamic values. So, my idea was to create another Zap (this third one) to do the following: 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. 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: If you are looking for a more custom solution, we do have a Zapier Experts program where you can get in touch with someone who can help set up Zaps.Here's another unconventional use case built with Airtable and Zapier: a retweet scheduler. Learn more about all of the social media apps Zapier supports. Social media channels like Facebook Pages, Instagram for Business, and LinkedIn allow you to create new posts with Zapier.Learn more about the social media management and marketing apps Zapier supports. Social media management apps like Buffer and Hootsuiteallow you to post to Twitter automatically.In order to keep using Twitter in your workflows, here are some suggestions: ![]() Users can access their Zaps using Twitter in view-only mode until September 30. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |