Add Custom AI buyers to your email list with Make

What you'll need

• A published Custom AI product (how to sell your Custom AI).
• A Make account.
• An account with your email platform, connected to Make.

Step 1: Create the webhook in Make

1. 01

   Start a scenario

   In Make, click Create a new scenario. Click the first module slot, search Webhooks, and pick Custom webhook.

2. 02

   Add a hook

   Click Add, give it a name like Eden purchases, and save. Make shows a URL that starts with https://hook.…make.com/…. Click Copy address to clipboard.

3. 03

   Leave Make waiting

   Make now listens for a first request so it can learn the fields. Keep this tab open.

Step 2: Paste it into Eden

1. 01

   Open your sales dashboard

   In Eden, go to Custom AIs → Sell your AI → Open sales dashboard, or open app.eden.so/sales.

2. 02

   Save the URL

   Scroll to Automations, paste the Make URL, and click Save and turn on. Eden shows a signing secret. Make does not need it.

3. 03

   Send a test

   Buy or claim one of your products with a different email. Back in Make, the webhook says Successfully determined and now knows the fields: buyerEmail, productTitle, event, status, and more.

Step 3: Add the buyer to your list

Click the plus after the webhook and pick your platform's module. Map buyerEmail to the email field and use productTitle as a tag.

Kit (ConvertKit) Module: Add a Subscriber to a Form or Add a Tag to a Subscriber. Map buyerEmail to Email.

Mailchimp Module: Add/Update a Subscriber. Pick your audience, map buyerEmail to Email Address, set status to Subscribed, and add productTitle under Tags.

beehiiv Module: Create a Subscription. Map buyerEmail to Email. Turn on Send welcome email if you want beehiiv's welcome to go out.

MailerLite Module: Create/Update a Subscriber. Map buyerEmail to Email and choose a buyers group.

ActiveCampaign Module: Create/Update a Contact, then Add a Tag to a Contact with productTitle.

Click Run once to check it with the test request Make already captured, then turn Scheduling on so the scenario runs immediately on every request.

Handling refunds

Add a second route after the webhook using a Router. Give it a filter for purchase.refunded and use your platform's Remove a Tag or Unsubscribe module. Many creators skip this and keep refunded buyers on the list.

If nothing arrives

• Check the URL in Eden matches the one in Make exactly. It must start with https://.
• If the webhook shows Not determined, send a fresh test purchase while the webhook is waiting, or click Redetermine data structure.
• The scenario has to be scheduled Immediately for new requests to run. Run once only processes one queued request.