How to Move a Thrive Automator Course-Access Recipe to Incoming Webhooks

In this article, you’ll learn how to move a Thrive Automator recipe that grants Thrive Apprentice course access from an outside tool over to incoming webhooks, which are built into Thrive Apprentice.

Incoming webhooks do everything that recipe did, plus guided field matching, a secret that protects every webhook from the start, a way to keep refunds from granting access, and a log of every request. Moving takes about five minutes.

Note: Incoming webhooks are available in Thrive Apprentice 11.1 and later.

Before You Start

Open your Automator recipe and note two things: which Thrive Apprentice product it grants, and which tool sends to it (for example, Zapier, ThriveCart, or your CRM). Keep the recipe turned on until the new webhook is working.

Moving Your Recipe

1. Go to Thrive Dashboard › Thrive Apprentice › Settings › Incoming Webhooks and add a webhook with the same product as your recipe. Choose Find or create user, then grant access to match what the recipe did.
2. Copy the new webhook URL and its secret. In your tool, replace the Automator webhook URL with the new one, and add the secret (most tools send it as a header).
3. Click Start Listening and send a test from your tool. Thrive Apprentice matches the email and name fields for you.
4. If your tool also sends refunds or cancellations to the same URL, add a condition on the Field mapping tab so this webhook only acts on purchases. Then duplicate the webhook, set the copy to Revoke access, and set its condition to refunds.
5. Save and activate. Make a test purchase, check the result on the Logs tab, then turn off the old Automator recipe.
6. If you had customized the New Account Created email, go to Settings › Email Templates and tick the Incoming webhook trigger so new students get your welcome email.

What’s Different From the Recipe

• The webhook lives inside Thrive Apprentice’s settings instead of a separate plugin.
• You can also choose to grant access to existing users only, or to remove access.
• Fields are matched automatically from a test request, a pasted sample, or a real request.
• Every webhook starts protected with a secret, and you can use signed requests for tools that support them.
• The Logs tab keeps 30 days of requests, and you can re-run any request after fixing a setting. See How to Read Incoming Webhook Logs in Thrive Apprentice.

Frequently Asked Questions

Can I run the recipe and the webhook at the same time?

Yes, briefly, while you test. If both receive the same sale, the student still ends up with one account and one set of access. Turn the recipe off once the webhook works.

Do I need Zapier or Make?

Only if your tool can’t send webhooks on its own. If it can, point it straight at the webhook URL.

That’s it! Your course-access recipe now runs inside Thrive Apprentice. For the full feature walkthrough, see How to Use Incoming Webhooks in Thrive Apprentice.