Skip to main content

Mailchimp & Webhooks: Connecting External Tools

Learn how to integrate Mailchimp for email marketing and configure webhook endpoints to track ticket sales, updates, and pending orders in real-time.

Looking to email your ticket holders, send a newsletter, or keep your attendee mailing list up to date? Posh connects directly with Mailchimp to automatically sync your buyer records as an email audience — no manual CSV exports needed. You can also use webhooks to push real-time sales data to external tools and CRMs.

Accessing the Integrations Workspace

To connect your external software ecosystem, navigate to your centralized settings panel:

  1. Click your Profile icon / Organization name in the top-right corner.

  2. Select Settings under the As an Organizer menu.

  3. Scroll down past your general organization parameters to locate the dedicated Integrations and Webhooks blocks.

Boost Your Marketing with Mailchimp

Integrating Posh with Mailchimp automatically syncs your buyer records, enabling you to launch targeted email campaigns without manually exporting CSV spreadsheets.

How to Set It Up

  1. Under the Integrations section, click the Connect button next to the Mailchimp logo.

  2. Log into your Mailchimp account in the secure pop-up window and click Allow to authorize the platform connection.

  3. Once connected, both your historical contact list and real-time Posh attendee check-ins will sync directly to your designated Mailchimp audience directory.

Launching Campaigns 🚀

Once active, navigate to your Attendees tab and click SMS Blast. Alongside your standard text messaging channels, Mailchimp will now be available as an outbound option to deploy email campaigns straight to your synchronized database.

Tracking Purchases in Real-Time with Webhooks

Webhooks push automated, instant data payloads (JSON) to external servers the exact second an action occurs on your event page. You can send ticket data to up to five webhook destinations at once and manage them in one place. Connect tools such as CrowdPass, Laylo, and your CRM alongside other destinations. Organizers also use webhooks to trigger alerts in Slack, add rows to Google Sheets, or sync profiles with external CRMs.

Understanding Your Triggers

You can toggle four distinct tracking triggers ON or OFF individually using your dashboard switches:

  • New order: Fires instantly when an attendee completes any successful order — including both paid ticket purchases and free RSVPs.

  • Order updated: Fires when a change hits a live registration (such as a refund, cancellation, or ticket transfer).

  • New pending order: Fires when a ticket is purchased but requires manual organizer verification.

  • Pending order actioned: Fires the moment a pending request is formally approved or denied by your team.

How to Connect Your Webhook Destinations

  1. Generate Your Destination Link: Log into your third-party automation tool (like Zapier). Start a new workflow using "Webhooks by Zapier" as the trigger, select Catch Hook, and copy the custom URL it generates (Note: Advanced webhook ingestion typically requires a paid Zapier plan).

  2. Paste into Posh: Return to your Posh Webhooks configuration card and paste that custom URL directly into the Webhook endpoint text field.

  3. Test & Audit: Click the Test button next to any trigger switch to push a mock sample payload to your server to verify the connection. If your developer needs to review the exact data formatting, click Copy code.

Critical Webhook & Accounting Realities

When mapping your webhook data to external tools or third-party tracking systems, keep these platform behaviors in mind to prevent data discrepancies:

⚠️ Important Data Alignment Rules:

  • Ticket Transfers: When a buyer transfers a ticket to a friend, the platform generates a fresh webhook payload. Do not calculate these as brand-new ticket sales. Look for the native ticket_transfer flag inside the data packet to cleanly isolate transfers from raw revenue.

  • Refunds & Disputes: Financial reversals do not delete previous data entries; instead, they trigger an Order updated event. Ensure your external CRM or database is configured to listen to status changes so it automatically deducts refunds from your custom external tallies.

  • Dashboard Discrepancies: Because transfers generate automated payloads and refunds update existing records rather than deleting them, your raw webhook counts may vary slightly from your live Event Dashboard counters. Always rely on your Posh Organizer Dashboard as your primary financial source of truth.

Did this answer your question?