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.

Hi everyone,

I'm using an invite-only integration for open-source Vtiger CRM in Zapier, and I'm running into an issue with a Zap that’s triggered on record updates.

My Current Setup:

  • Trigger: “Record Updated in Vtiger” (from the invite-only app) (we use Open Source VTiger)

  • Action: Email is drafted in Outlook

The problem is:

  • The Zap only triggers on the first update to a record.

  • Later updates to the same record don’t retrigger the Zap, even though the data is changing.

This is a blocker for us because we sometimes need to trigger downstream actions based on multiple distinct updates to the same record, not just the initial one.

What I Would Like:

  • A way to trigger the Zap on every update to a record (not just the first).

  • OR a workaround that ensures each relevant update on VTiger is seen as “new” by Zapier.

  • Bonus: Ideally without creating duplicate records or too much manual intervention.

Anyone have this issue and know a fix?

Hi ​@RJackson,

 

Welcome to the Community.

To ensure Zapier triggers correctly on every update to a record in Vtiger CRM, verify that the "Record Updated" trigger is monitoring all relevant fields. Implement a custom field, like a timestamp, to help Zapier recognize each update as a new event. If critical fields require individual attention, set up separate triggers for each. Webhooks can offer greater flexibility for triggering updates dynamically. Check Vtiger's documentation for potential integration limitations, and avoid duplicate records by testing thoroughly. Automate as much of the process as possible to streamline workflow efficiency. 

If you have any questions or need further assistance, feel free to ask.

Hi there ​@RJackson 👋

Just came across this and wanted to check how things are going. Did you have any success with Jammer’s suggestion of using Webhooks instead?

If not, you might be best off reaching out to the person who sent you the link to that invite-only Vtiger CRM app integration—presumably it was the app integrations’s developers? If so, they should have more insight into the trigger’s setup and be better able to help investigate things further. Happy to lend a hand if you need any help in setting up the Webhook trigger for the Zap though, just let me know! 🙂

That said, I spotted a feature request for the publicly available Vtiger CRM app to support self-hosted versions of Vtiger. Would you like me to add your vote to that feature request?

Looking forward to hearing from you! 

Terms & Conditions