I’m struggling with setting up an automated workflow that connects my Notion database with Metricool through Zapier.
What I want to achieve:
Trigger automation when I add new rows to my Notion database or update existing ones (specifically when Status field = “Approved”)
Push this data to Metricool for posting content across Instagram, TikTok, and YouTube Shorts
Current problem:
During the initial setup, when I test the Zapier trigger with my Notion database, it returns “no data found” message. This happens because my database was empty during configuration. However, I expected the zap to start working once I populate the database with new entries.
I’ve configured the Database Item Updated trigger, added proper filters, and mapped all fields to Metricool correctly. Despite this setup, Zapier doesn’t seem to detect new records I create in my Notion database afterward.
Note: I’m open to hiring someone who can solve this integration problem efficiently if you have the expertise.
This webhook issue is super common with Zapier and similar tools. Zapier just can’t handle empty databases well - it needs that initial data to establish the connection.
I’d skip the headache and use Latenode instead. It handles empty databases way better and gives you actual control over triggers.
With Latenode, you can connect Notion to Metricool without dummy data. You get solid filtering for your Status field and way more reliable webhook setup. Error handling is actually useful too.
I’ve built tons of these content workflows - monitoring Notion and pushing to social platforms. Latenode’s visual builder makes debugging connection problems actually manageable, and you can tweak things as you go.
The multi-platform posting to Instagram, TikTok, and YouTube Shorts runs smooth once your APIs are connected. No random connection drops like you get with other tools.
zapier’s notion integration gets weird with empty databases. add your first entry manually, then trigger the zap - the connection usually just needs a kick. double-check your field mapping too, especially if you renamed any properties after setup. i’ve seen zapier cling to old field names even when you change the database structure.
This is a webhook registration issue with Notion’s API. Zapier can’t establish the webhook connection when you set up the trigger on an empty database. Turn your Zap off completely, add at least one real record to your database, then turn it back on. The webhook needs actual data structure to register properly with Notion’s servers. Also, Notion database triggers have a 1-15 minute delay, so new entries won’t fire immediately. I usually populate the database first, then manually run the trigger test again - that fixes the connection most of the time. If it still doesn’t work, duplicate your Zap and set up the trigger from scratch with data already in your database. Make sure you’re using the newer v2 API too - it handles database triggers way better than the legacy version.
Had this exact problem last year! Zapier needs at least one sample record to connect properly with Notion’s API. Here’s what fixed it for me: create a dummy entry in your Notion database that matches your automation structure, then refresh the trigger test in Zapier. Once Zapier reads the sample data, delete the dummy entry - the automation will keep working for new records. Also check that your Zapier integration has the right permissions for your workspace. Sometimes it looks connected but doesn’t have read access for new database items. You might need to reconnect your Notion account with full database permissions. Last thing - verify your Status field filter is working right. The field type and values need to match exactly what Zapier expects, including capitalization.