When webhook data received, get subscriber details from MailPoet, and return it in the webhook response
Turn your WordPress site into a small lookup API: another app posts to a FlowMattic webhook, the workflow fetches that subscriber’s details from MailPoet, and returns them in the webhook’s reply.
Webhook
MailPoet
Webhook Response3 steps Setup ~5 min Used on 2.8k sites Free to import
What this workflow does
MailPoet keeps your subscribers inside WordPress, which is handy until another tool needs to read them. A support desk, a member app or a custom script might want to know whether someone is subscribed and what MailPoet holds about them. This workflow answers that question on request.
The first step is a FlowMattic Webhook trigger with its own URL. The calling app sends a request to the workflow's URL and includes the details that identify the subscriber, such as an email address. The MailPoet step uses Get Subscriber Details to look up that existing subscriber. The Webhook Response step then sends back the data you map from the lookup, so the caller receives it as the reply to its request.
Because this returns subscriber data, protect the endpoint. Turn on the Webhook trigger's "Require authentication on incoming requests" setting so only callers with your key or a valid signature get an answer. Without it, anyone with the URL can query your list.
Help desk subscriber check
Your support tool calls the webhook with a customer's email and shows the agent what MailPoet holds about that subscriber.
Custom app on another server
A members' app outside WordPress asks the endpoint for a person's MailPoet details before it shows newsletter options.
No-code tool lookups
An automation in another platform sends an HTTP request to this webhook and uses the returned MailPoet data in its own next step.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Webhook Capture Webhook ResponseGives the workflow a URL that other apps call. The request should carry the details that identify the subscriber, which become available to the MailPoet step.
- MailPoet Get Subscriber Details
Looks up an existing MailPoet subscriber using the identifier from the request. Map the value the step asks for from the webhook data, and test with a known subscriber.
- Webhook Response Set Webhook Response
Sends the MailPoet lookup result back to the caller as the webhook reply. Choose which subscriber details to include and leave out anything the caller shouldn't see.
What you need
- FlowMatticCore
- MailPoet PluginPlugin
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Turn on "Require authentication on incoming requests" in the Webhook trigger and give the calling app the key, so the subscriber lookup isn't open to anyone.
- Return only the MailPoet details the caller actually needs instead of everything the lookup gives back, to keep the reply small and private.
- Send a test request with the email of a known subscriber after import, so FlowMattic captures the request and the MailPoet response for mapping.
Questions about this workflow
What does the reply contain if the MailPoet subscriber isn't found?
The lookup step returns MailPoet's error or an empty result, and the Webhook Response sends back whatever you mapped. Test with an unknown address and check Task History so the caller can handle that case.
Can the MailPoet lookup create subscribers too?
Not as imported. Get Subscriber Details only reads. MailPoet's Create New Subscriber action is available if you want a separate workflow for adding people.
Is MailPoet data exposed to anyone who finds the webhook URL?
Not when the trigger's authentication setting is on. With it on, callers must send your key or a valid signature. With it off, anyone holding the URL could ask for subscriber details.
Does the calling app wait for the MailPoet data?
Yes. The Webhook Response step sets the reply to the incoming request, so the caller receives the subscriber details as the response.
More Email Marketing workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted