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.

Question

ManyChat "Trigger a Zap" Action - Zapier doesn't show my test records during setup

  • May 28, 2025
  • 3 replies
  • 39 views
S

I’m trying to setup a very simple zap to capture an email registration but can’t get beyond the initial setup.  The problem is Zapier not show my event test under “Find new records”.  

 

Manychat triggers the event using “Trigger a Zap”.  I’ve run multiple tests and can verify everything is working properly within Manychat.  The flow works and the zap gets triggered within Manychat, but the event record isn’t shown within Zapier.

 

Even more strange -- Zapier show erroneous “new records” under the “Test” tab.  These false records are happening even though there is not active flow to allow it.  

 

I found a prior community post from 8 months ago that shares the same problem.  Unfortunately, Support acknowledged the problem was happening to many users but then closed the case without resolving it. Hopefully someone can help me out with this.

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Troy TessaloneZapier Orchestrator & Solution Partner
  • Zapier Orchestrator & Solution Partner
  • 34072 replies
  • May 28, 2025

Hi ​@sowetoddid 

Most Zap app integrations are created and managed by the app developer using the Zapier Developer Platform.

You may find this Zapier help link useful for getting test records to use: https://help.zapier.com/hc/en-us/articles/35632951078029-Use-previous-Zap-runs-as-trigger-test-records

You may want to try reaching out to Manychat Support for possible help.

⚡ Troy Tessalone - AutomationAce.com | Platinum Authorized Zapier Solution Partner | #1 Zapier Community Contributor
S
  • sowetoddid
  • Author
  • New
  • 1 reply
  • May 28, 2025

Thanks for the quick response Troy.  I haven’t received a solution from Manychat (yet).  

That said, your link solved the problem.

 

For others with the same problem -- I selected one of the erroneous test records just so I could finish the setup and publish the zap.  After publishing it, I triggered my Manychat flow again.  I found my successful “Zap run” and marked it for use as a “test record”.  I went back and edited the zap to use that test record.  

JammerS
Forum|alt.badge.img+6
  • JammerSZapier Staff
  • Zapier Staff
  • 3527 replies
  • May 29, 2025

Hi ​@sowetoddid,

 

Thank you for sharing your experience and solution with the community to Manychat integration issue using a workaround. First, complete and publish the Zap setup with any available test record. Then, trigger the Manychat flow to generate a correct record. Locate the successful Zap run in Zapier's Zap History and mark it as a test record. Finally, edit the Zap to use this correct test record, ensuring proper configuration. This method helps bypass setup hurdles while maintaining accurate data. Let me know if you need further refinements.

Feel free to ask if you have questions or need further assistance with Manychat or any other integrations. We're here to help.

Terms & ConditionsAccessibility statement