Workflow & automation connectors
Which recipes send customer data to outside apps?
Automation helps with orders, CRM updates, and notifications. Workflows connected to outside apps or webhooks can share order details, form submissions, and user data. Compare the documented setups below.
Based on plugin and vendor documentation, not tests of your site. Your active recipes decide the path. This is not legal advice or a compliance rating.
Scan your site for third-party requestsThis scan checks requests made by a visitor's browser. Server-side automation / webhook traffic does not appear in a browser scan. Inventory each recipe's external endpoints.
On-site actions vs data sent elsewhere
Inventory what each recipe does
List active workflows, the data they use, and where it goes. Separate updates to posts or roles from steps that send data to outside services. Check email delivery separately. Keep useful automation; document its destinations.
Recipes that forward data off-site
Connected apps can receive names, emails, addresses, and order or form fields, depending on the workflow. Check each destination's retention settings and policy. These server-to-server transfers do not appear in a visitor's browser scan.
Automation plugins and connectors
No paid placement. Vendor-egress rows first, then setups not yet reviewed. Names are alphabetical within each group.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| FlowMattic Commercial WordPress workflow builder. Vendor materials describe connecting site events to integrations and webhooks so order, form, and user data can be forwarded to outside apps when a workflow runs. That path is server-side and not visible in a visitor browser scan. Exact endpoints depend on the workflow you configure. | Can forward site data to outside apps or webhooks | Outside browser-scan scope | Not assessed | Not tested |
| |
| OttoKit (SureTriggers) Documented as an all-in-one automation platform connecting WordPress plugins and outside apps (CRM, accounting, Drive, Slack, WhatsApp, and more). Example flows add order customers to a CRM and forward order details off-site. When a workflow includes an outside-app step, personal and order data can leave your server when the workflow runs. Not a visitor browser host. | Can forward site data to outside apps or webhooks | Outside browser-scan scope | Not assessed | Not tested |
| |
| Thrive Automator Documented automations connect WordPress events to outside apps (email marketing tools and other Thrive-listed integrations), for example adding buyers to a list or tagging commenters in an ESP. When an automation includes an outside-app action, customer or visitor details can leave your server when the workflow runs. Listing notes a migration path toward Uncanny Automator. Not a visitor browser host. | Can forward site data to outside apps or webhooks | Outside browser-scan scope | Not assessed | Not tested |
| |
| Uncanny Automator Documented recipe builder connects WordPress triggers (orders, forms, LMS events) to actions in outside apps and webhooks, for example pushing form submissions and site activity to Google Sheets, a CRM, Slack, Mailchimp, HubSpot, or any webhook endpoint. When a recipe includes an outside-app or webhook action, that data can leave your server when the workflow runs. Not a visitor browser host. | Can forward site data to outside apps or webhooks | Outside browser-scan scope | Not assessed | Not tested |
| |
| WP Webhooks Documented Trigger (Send Data) path sends information from WordPress on a specific event (for example a form submission or user login) to any API or external service you choose (Zapier, Make, Pabbly, custom endpoints). The payload is whatever fields the trigger includes. Server-side, not a visitor browser host. | Can forward site data to outside apps or webhooks | Outside browser-scan scope | Not assessed | Not tested |
| |
| Zapier for WordPress Zapier connects WordPress events, such as new users, comments, and posts, to other apps. Depending on the trigger, Zapier checks for new data or receives an instant update. A configured Zap can share that data with another app. This server-to-server path is outside a visitor's browser scan. | Can forward site data to outside apps or webhooks | Outside browser-scan scope | Not assessed | Not tested |
|
What this table does and does not prove
This table describes documented workflows, not tests of your site. Consent timing and data retention have not been assessed. Check your active workflows, destinations, and provider agreements.
Documentation snapshot: Oct 8, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress forms privacy
- WordPress CRM plugin privacy
- WordPress marketplace plugin privacy
- WordPress SMTP plugin privacy
- All privacy guides
/wp-automation-plugin-privacy