Skip to main content

Im unable to export all my contacts information for a re-engagement campaign. There is no “Bulk Action” allowing me to bulk export my contacts. 

Hello ​@jessesteele ,

There isn’t a button to do this automatically, but you can easily achieve it by creating a flow that exports the contact data to a Google Sheet. This article from Manychat explains how to use the native integration between Manychat and Google Sheets:

https://help.manychat.com/hc/en-us/articles/14281248811292-Google-Sheets-integration

Also, take a look at this post where I shared some additional tips to help avoid errors when exporting data to Google Sheets:
https://community.manychat.com/general-q-a-43/contact-id-6804
 


but how do i export all historical data? that seems to be going forward. 


In this post (https://community.manychat.com/general-q-a-43/contact-id-6804), I explained the details of how to do it — take a look. But to summarize:

  1. The first step is to create a flow that exports each contact’s information individually to a spreadsheet.

  2. The second step is to create a sequence that sends this flow immediately to the contact.

  3. The third step is to go to your contact list and select all of them.

  4. The fourth step is to add all these contacts to the sequence you created.


ok so create an automation? this is very confusing and unclear for new users 

as i understand 

Creating the flow: 
create automation >  trigger “contact event occurs” > action create google sheet

 

Creating sequence: 
create sequence, select automation above, turn toggle active on? then go to contacts, select all, add to this sequence? 


Sorry for the confusion, here’s a clear message. 
 

The issue is that ManyChat only exports the most recent interaction per user. If a contact opts into multiple flows or comments on several different posts, I only get one row of data, not multiple.

For my re-engagement campaign, I need every instance of opt-in activity, even if it’s from the same contact.

🔄 What I Want:

I need a way to:

  • Export all opt-in events, even if the same user.id appears more than once

  • Treat each trigger (e.g. Instagram comment) as its own data row

  • Include details like optin.source, timestamp, and which post/comment triggered it

This is critical because it allows me to:

  • Detect high-intent users (those who opted in twice)

  • Trigger custom follow-ups in ManyChat or Zapier

  • Segment users who’ve already seen a lead magnet vs. those who haven’t

🙏 How You Can Help:

  1. Is there a way in ManyChat to log/export every opt-in event, not just the latest user state?

  2. Can we trigger the Zapier webhook or store a row each time a specific comment trigger fires, regardless of whether the user already exists?

  3. Can you confirm that the optin.source value gets updated and sent every time a new automation is triggered?


Hi ​@jessesteele ,
Thank you for the detailed explanation—now I fully understand what you need.

Regarding your first question, it’s true that in the contact data, Manychat only provides the most recent opt-in event, not the full history. What you can do is start saving this information from now on, but for historical data, you’ll only be able to access the most recent event for each user.

As for your second question, yes, it’s definitely possible to send data to Zapier whenever the trigger is activated. To do that, set up your comment trigger so it sends a reply via direct message. Then, within the direct message flow, add a step that makes an external request, sending the contact’s data to Zapier. The value in the "last_growth_tool" field will correspond to the automation the user just entered. Your Manychat flow will look something like this:
 

Regarding your third question, that’s exactly right. Just a heads-up: make sure the user actually interacts in the direct message—either by clicking a button or replying to a message. I ran some tests where the automation sent just one message, and in those cases, the "last_growth_tool" field wasn’t updated. It was only updated correctly in flows where the user interacted with the automation.
 


Reply