> For the complete documentation index, see [llms.txt](https://themochi-app.gitbook.io/mochi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://themochi-app.gitbook.io/mochi-docs/feature-and-settings/integrations/zapier-integration.md). # Zapier Integration Connect your Mochi account to over 5,000+ apps like Google Sheets, Slack, HubSpot, and more using Zapier's automation platform. ## What It Does The **Zapier Integration** automatically sends lead updates and payment events from Mochi to any app you choose through Zapier. When something important happens in your Mochi account—like a new lead coming in, a lead getting qualified, or a payment being received—Zapier instantly triggers actions in your other tools. You can use this integration to build powerful automations like adding qualified leads to your CRM, sending Slack notifications when payments come in, updating Google Sheets with lead data, or creating tasks in your project management tool when leads book calls. The integration respects Instagram's privacy policies by only sharing lead metadata (usernames, contact info, funnel status, tags) and never sharing message content or AI-generated conversation summaries. Webhooks are delivered within seconds of events happening in Mochi, with automatic retries to ensure reliable delivery. If a Zap gets turned off in Zapier, Mochi automatically stops sending webhooks to prevent unnecessary processing. ## Setting It Up ### Step 1: Connect Your Mochi Account 1. Log into your Zapier account at zapier.com 2. Create a new Zap or edit an existing one 3. Choose "Mochi" as your trigger app 4. Select the trigger event you want (like "New Lead" or "Lead Status Changed") 5. Click "Connect" and authorize Zapier to access your Mochi account 6. Choose which Mochi organization to connect if you have multiple ### Step 2: Configure Your Trigger Pick from these available triggers: * **New Lead** - Fires when a lead first enters your funnel * **Lead Status Changed** - Fires when a lead moves between funnel stages * **Lead Won** - Fires when a lead is marked as won/closed * **Lead Lost** - Fires when a lead is marked as lost * **Payment Created** - Fires when any new payment is created * **Payment Paid** - Fires when a payment is marked as paid ### Step 3: Set Up Your Action Choose what should happen when the trigger fires. Popular actions include: * Add lead data to Google Sheets * Create contacts in your CRM * Send notifications to Slack or Teams * Create tasks in project management tools * Send emails through your email platform ### Step 4: Test and Turn On Test your Zap to make sure it's working correctly, then turn it on to start automating your workflows. ## How to Use It ### Lead Automation The integration sends detailed lead information including Instagram username, name, profile picture, current funnel status, source information, tags, contact details, and assigned setter/closer. You'll also get the automation name that captured the lead and any unqualify reasons if applicable. For **Lead Status Changed** triggers, you get both the current status and previous status so you can track exactly how leads are moving through your funnel. ### Payment Automation Payment webhooks include the payment amount, type (full payment, installment, or deposit), status, due dates, and related lead information. For installment payments, you get details about all installments in the series including their individual due dates and amounts. ### Organization Stats You can also pull organization performance data on-demand using Zapier actions, including lead metrics for any date range up to one year. ## Tips * Start with simple automations like lead notifications before building complex multi-step workflows * Use lead tags to filter which automations should trigger for specific types of leads * Set up separate Zaps for different lead sources or funnel stages to keep your automations organized * Test your Zaps thoroughly before going live to avoid sending incorrect data to your other tools * Monitor your Zap history in Zapier to catch any delivery issues early * Only team creators and managers can authorize the Zapier integration for security reasons --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://themochi-app.gitbook.io/mochi-docs/feature-and-settings/integrations/zapier-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.