Linking Manychat and Sytem.io via Zapier

Question

I’m currently experiencing an issue with an automation connecting ManyChat to Systeme.io through Zapier.

The workflow I’m trying to achieve is the following:

Instagram → ManyChat → Zapier → Systeme.io

A user comments on an Instagram post, enters a ManyChat automation, and provides their email address. Zapier should then retrieve this email and create or update the contact in Systeme.io, while also assigning the appropriate tag.

The problem is that the information collected in ManyChat, particularly the user’s email address, is not being transferred correctly to Systeme.io through Zapier.

The email is correctly captured and visible inside ManyChat, but somewhere between ManyChat and Systeme.io the data does not seem to be passed or mapped properly.

My Zap currently uses:

Trigger: ManyChat
Action: Systeme.io — Create/Update Contact
Email field: ManyChat User Email
Tag: assigned to the relevant campaign/freebie

I would appreciate your help checking whether the issue comes from the ManyChat trigger, the field mapping in Zapier, or the Systeme.io action.

I have been looking on the Community to find a solution but unsuccessful.

Could you please let me know what information or screenshots you need from me to investigate this?

Thank you in advance for your help.

Best regards,

Chris

SumGenius · Answer

You can split this in half in a minute without sending anyone screenshots. Open the Zap in Zapier, go to task history, open one run, and read the trigger data ManyChat actually sent. Blank email there means the problem is in ManyChat. Populated there means it's your mapping or the Systeme.io action. Everything else is guesswork until you know which half you're in.

If it's blank, two things to check.

Order of blocks. ManyChat runs a flow top to bottom, so whatever sets the email has to sit above the Zapier action. If the Zap fires first or alongside, it sends the contact as it was a moment earlier, which is empty.

Where the email landed. If your User Input saved to a custom field rather than the system Email field, it looks right inside ManyChat but is much less reliable going out. Zapier only surfaces a limited number of custom fields from ManyChat and they often come through null. Add a Set User Field step writing to the system Email field and map from that.

If it's populated in task history, then it's the Systeme.io step. Most likely the mapping was built from a test sample with no email in it, so re-run the trigger test with a contact that definitely has one and remap the field.

Sign up

Welcome to the Manychat Community!