There are also many Make experts hanging out there who can answer other Make questions. However, the one downside to Make is that there can be a bit of a learning curve with Make, which is why I created this basic navigation video for Make, along with providing the link to Make’s free training courses. Make has much better tech support than Zapier. Make is SIGNIFICANTLY cheaper than Zapier, even though it is way more powerful than Zapier.Ĥ. ![]() For example, Make has an entire library of hundreds of functions & tools built into the platform that let you manipulate your data in ways that Zapier doesn't allow at all - including groups of Airtable records at once, which Zapier also doesn't allow.ģ. Make is SIGNIFICANTLY more powerful than Zapier. Also, Make has a purely visual drag-and-drop environment that makes it much easier to visualize entire automations.Ģ. Just as one example out of dozens of examples, Zapier only allows 3 conditional branches, whereas Make allows unlimited conditional branches. Zapiers automation tools make it easy to connect Airtable and Number. Make has none of the limitations that Zapier has. Set up the Airtable trigger, and make magic happen automatically in Number. The main problems that I have with Zapier are best described by discussing the main advantages that Make has over Zapier:ġ. I would always recommend using Make over Zapier. I was curious if anyone had a technical solution for this issue, or perhaps a more logistical correction if I’m thinking about the structure of my base incorrectly.Mentioned Zapier, but I would not recommend using Zapier. The simplest solution seems to be somehow adding multiple records from separate integrations to a single field, but that doesn’t currently seem like an option either. That tracks every conversion, but means I have a million columns on my Contact table – and my gallery view (which the recruiters are using) isn’t as clean as I’d like it to be.īecause we deal with thousands of contacts in a year, manually adding each conversion point is not an option. My current workaround is to have a column for every single type of conversion on my Contacts table – which is either blank, or filled with the conversion value (so, a column called General Web Form that receives the value General Web Form if triggered by the integration. Here, well dive into how to collect responses with a. Ideally, those conversions would stack up in the same field (linking to multiple records). Setting up automated workflows with Zapier puts an end to repetitive tasks, saving you and your team time. ![]() Zapier can locate the record, and then updated it – but If I use the same trick, the integration will overwrite the existing data in the linked records field, so I lose the General Web Form conversion. The challenge is at the second point of conversion: let’s say Event Registration. ![]() So if a candidate fills out the General Web Form, I can have a unique Zap with the text ‘General Web Form’ dropping into the linked records -> Interactions field and it works like a charm. I have a Contacts table (with Email as the unique identifier), and an Interactions table (with things like General Web Form, Event Registration, etc.). Zapier lets you connect Airtable with thousands of the most popular apps, so you can automate your work and have more time for what matters mostno code required. The primary challenge I’m encountering is in logging interactions. We’ve used Zapier for ages to create and update records in Google Sheets, and are shifting our process over to Airtable to allow more users access to the data. Hello! I work in higher ed, and am trying to set up a highly automated CRM base.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |