ManyChat IG Lead Magnet walks an agent through the full path from an Instagram post to a delivered resource: picking trigger keywords, preparing the PDF or link, duplicating a working ManyChat automation, adding tracking tags and writing the DM and consent copy.
Delivery is gated on explicit newsletter consent and a verified subscribed status. Anything external-facing, such as updating a live flow or sending a Slack message, waits for explicit approval.
What You Get
- One primary keyword and two to four backups, with a list of terms too broad to use
- A launch packet with DM copy, email capture and consent copy, tracking tags and fields, and an attachment plan
- A ManyChat automation duplicated from a working base, with the trigger, tracking and DM sequence set
- A test matrix that covers consent declined, invalid email, pending confirmation and returning subscribers
- A final report of what was prepared, what changed, the evidence checked and the approval still needed
Common Use Cases
- Offering a PDF or guide to people who comment a keyword on a reel
- Adding a separate Story reply trigger for the same resource
- Triaging resource requesters across client, partnership, sponsorship, M&A and recruiting lanes with a human reviewing the result
What Makes It Unique
Most lead magnet recipes send the file as soon as someone comments. This one holds the resource until a supported readback shows the person is subscribed to the right publication, treats API or Zap acceptance as weaker evidence than subscribed status, never reactivates an unsubscribed contact, and separates a saved flow from a published one from an enabled trigger. Lead-fit tiers stay advisory and unknown is kept apart from a mismatch.
Under The Hood
The skill is instructions plus four reference documents and no scripts. It tells the agent to run the repository’s version check script from the shell and to follow the user’s existing telemetry choice. The ManyChat steps are driven through a browser or computer-use session, where the agent signs in, edits automations and checks saved state, and the user completes any login or passkey prompt. The agent may build a PDF with an available builder, host a file, inspect a Zapier run history and read back newsletter status. It must stop for explicit approval before sending Slack or email messages, uploading to a live flow, publishing, enabling a trigger or changing account permissions.