![]() You have to set up an individual zap for each possible change to a data table (e.g., you need to set up zaps for record additions, record updates, field additions, etc).Want to automatically add new Facebook message inbounds to your CRM? There’s a zap for that.įor these sorts of use cases, Zapier is top of class.īut Zapier is not a great tool when it comes to simple data syncing. Want to automatically save email attachments to your Google Drive? There’s a zap for that. These days it seems like Zapier needs no introduction, but in case you haven’t used it yet: Zapier is a low-code way to automate event flows between tools. Want to use Zapier to do this? It’ll be harder than you think. Pros: Maximum flexibility & control, tailored to your use caseĬons: Requires valuable engineering resources to build and maintain (which these days cost companies up to $150 / hour, plus the opportunity cost of your engineers’ time), not scalable, no customer service when things go wrong or your data schema changes Often things break at the worst times, as any developer knows :) For technical teams, this may distract from product development, especially if the script requires maintenance over time. However, writing these scripts is a technical process that might be too high a boundary for nontechnical teams. Both Airtable and Notion offer APIs through which you can read and write data (although for Airtable you need the Enterprise plan to get access to webhooks and the metadata API, so we recommend using BaseQL instead). If you’re just doing one-way syncs, it may be enough to work with the APIs built into your tools and databases. After all, why pay for something you could do yourself? ![]() Incomplete or mismatching data, constant requests to engineers… sound familiar? Below, we talk through 4 different ways to sync between Airtable/Notion and your backend DB.įor some teams, the knee-jerk method is to build an internal script. Instead, your engineers are constantly fielding requests for CSV exports, distracting them from product development. Ops: Your ops team needs to be able to contextualize reasons for missed deadlines, but your SLA data is syncing in MongoDB and your ops team doesn’t know how to edit that data directly.You can consolidate that data in your Postgres database, but it’s still not touching Notion, so your Notion view is incomplete. Customer success: Notion is your customer success HQ, but you have customer data across a ton of sources (Amplitude, Stripe, Zendesk, etc). ![]() ![]()
0 Comments
Leave a Reply. |