1. Home
  2. Knowledge Base
  3. Thrive Automator
  4. Automation Recipe Books
  5. Automation Recipe Book: 3rd Party Integrations

Automation Recipe Book: 3rd Party Integrations

Connect Thrive Themes with your favorite external tools, form plugins, and payment processors using Thrive Automator.

Thrive Automator is now Legacy. We have partnered with Uncanny Automator for all future website automation needs. Learn how to switch to Uncanny Automator.

The below given triggers may no longer be available in the plugin.


1. Third-Party Form Plugins

If you prefer using other form builders, you can still use their submissions to trigger Thrive Automator workflows.

Recipe: Create WordPress Users from Happyforms

  • Goal: Automatically register a new user when they submit a Happyforms form.
  • Trigger: Happyforms -> “Happyforms form submit”
  • Action: WordPress -> “Find or create user”
  • Setup: Map the email and name fields from Happyforms to the WordPress user profile.

Recipe: Build a Mailing List with Elementor Forms

  • Goal: Connect Elementor forms to autoresponders or CRMs like Encharge.io.
  • Trigger: Elementor -> “Elementor form submit”
  • Action: “Add user in autoresponder” OR “Send Webhook”
  • Setup: Select your specific Elementor form as the trigger and map the fields to your chosen action.

Recipe: Grant Course Access via Ninja Forms

  • Goal: Create a user account and grant Apprentice product access when a Ninja Form is submitted.
  • Trigger: “Incoming Webhook” (See the Data Flow guide for setup details).
  • Setup in Ninja Forms: Use the Ninja Forms “Webhooks” action to send data to the Thrive Automator URL.

2. Events & Booking Integrations

Automate your scheduling and event management by connecting booking plugins to your marketing stack.

Recipe: Notify Slack for Amelia Bookings

  • Goal: Get instant team alerts when a new appointment or event is booked in Amelia.
  • Trigger: Amelia -> “Event Booking Created” or “Appointment Booking Created”
  • Action: Slack -> “Send Notification”

Recipe: Trigger Automations from Events Manager

  • Goal: Perform actions (like sending an email or tagging a user) when an event is published or a booking is added.
  • Triggers: Events Manager -> “Booking added”, “Event published”, etc.

Recipe: Sync Conversions with Facebook Events

  • Goal: Fire a Facebook Pixel event (Standard or Custom) when a user performs an action on your site.
  • Trigger: (Any, e.g., “User leaves comment” or “Form submit”)
  • Action: Facebook Marketing API -> “Fire Facebook standard event” (e.g., Lead, CompleteRegistration)

3. Selling Products & Payments (Webhook-Based)

Connect external checkouts and payment processors to Thrive Apprentice products.

Recipe: Sell Courses via Stripe, PayPal, or ThriveCart

  • Goal: Automatically grant access to an Apprentice product after a successful payment on an external platform.
  • Trigger: “Incoming Webhook”
  • Action 1: WordPress -> “Find or create user”
  • Action 2: Thrive Apprentice -> “Grant access to product”
  • Setup Guides:
  • Stripe: Set up a Webhook in the Stripe Developer dashboard to listen for checkout.session.completed.
  • PayPal: Use the Instant Payment Notification (IPN) feature in PayPal to send data to your Thrive Automator URL.
  • ThriveCart/Digistore24: Use their native Webhook/IPN integration settings to point to Thrive Automator.

Recipe: Grant Access via Studiocart

  • Goal: Connect the Studiocart checkout plugin to Thrive Apprentice.
  • Trigger: Studiocart -> “Order created”
  • Action: Thrive Apprentice -> “Grant access to product”

4. Advanced Data & Multi-Site Workflows

Recipe: Log Testimonials to Google Sheets (via Zapier)

  • Goal: Centralize all social proof in a spreadsheet for easy review.
  • Trigger: Thrive Ovation -> “User leaves a testimonial”
  • Action: “Send Webhook”
  • Setup: Use a “Catch Hook” in Zapier as the destination. Map testimonial data (Name, Website, Content) to the webhook fields.

Recipe: Connect Two Different WordPress Sites

  • Goal: Trigger an action on “Site B” when an event happens on “Site A”.
  • Site A (Source): Trigger (e.g., “Form submit”) -> Action: “Send Webhook”
  • Site B (Destination): Trigger: “Incoming Webhook” -> Action (e.g., “Grant access to product”)
  • Workflow: Copy the Incoming Webhook URL from Site B and paste it into the Send Webhook action on Site A.
    “`_
Was this article helpful?

Related Articles

>