Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Ok - I have admitted I need help. This workflow works perfectly in testing, but once published I can’t get it to do boo. I have tried updating the database, creating new entries in the database - nothing seems to work. I’ve got to think it’s something to do with the trigger, which I’ve never used before. 

The workflow is the below:
 

  1. Trigger:

    • Updated Data Source Item in Notion, connected to by job application database. This retrieves some basic data from the database such as name, email etc for each of my applicants.

  2. Retrieve Related Data:

    • Retrieve a Page in Notion, specifically to extract some content that is used to craft the email, such as email copy and proposed interview slots. I don’t know why this doesn’t come through with the trigger, but it does seem to come through with the retrieve a page operation. 

  3. Filter the Trigger:

    • Only proceed if the a select column in the database (“send invitation for screening interview”) reads “yes”

  4. Send an Automated Email via Gmail:

    • Send an email using Gmail.
    • The to, cc and subject fields are pulled from the database, as well as the email content. 

       

Hey ​@DevonLong,

Please check Zap run history for Live Zaps. See if there is any data there. 

Can you post screenshots of Data In and Data Out as well as how each Zap step is configured for us to have more context?

Yes - in zap history, I can see the zap has a number of live runs. They are all generally being filtered out as expected. 
 

 

Here is how it’s configured

connects to my database which has zapier connection enabled
Uses page ID retrieved in previous step to collect additional details


 

I have double checked, the “select” options in this column are “yes” and “no” - so I haven’t made a spelling or capitalisation discrepancy mistake

This post has been edited by a moderator to remove personally identifiable information (PII). Please remember that this is a public forum and avoid sharing personal or potentially sensitive details.

Hi ​@DevonLong, I would suggest combining Notion’s database automations with the Webhook trigger step in Zapier, rather than using the Updated Data Source trigger in Notion’s Zapier integration.

This carries a few benefits:

  1. More fine-grained control over when the automation runs, because you can define the combination of events in a Notion database record that should actually trigger sending the webhook to Zapier
  2. As seen in the screenshot, with this action you can customise which properties from your database that get sent to the webhook and Zap. This can make building your Zap easier, as the trigger payload isn’t overrun with every single property from your Notion database. 
  3. Reliability - I find that Zap run more consistently with this approach, because they’re only being triggered when a specific combination of conditions in my source database is met, rather than firing for every possible change in the database and then filtering down within the Zap.

Hope if this helps, and if you need any further pointers on how to set this up, just let me know.

 

 

​@LannyAva - you do this by configuring the trigger event(s) in your Notion database that you want to start the automation. You can filter based on any property in your database, and when selecting multiple triggers, you can define whether all conditions have to be met, or if you want the automation to run as long as any of the conditions are met:

 

Hey ​@DevonLong,

Update Data Source Item trigger for Job Application form will only trigger when you update your Job Application Form. Try using New Data Source Item trigger if you want it to trigger for new entries.

 

Hope it helps!

Terms & ConditionsAccessibility statement