# Workflow Automation DPA Subprocessors: 2026 Guide

By Alex Kim · 2026-11-22 · Source: https://www.activepieces.com/blog/workflow-automation-dpa-subprocessors-2026-guide

---
<aside class="tldr"><p class="tldr-label">Summary</p><p>Workflow automation platforms vary widely in public DPA confirmation, with most requiring direct vendor requests and self-hosting (n8n, Activepieces) eliminating subprocessor vendor control.</p><ul><li>Missed subprocessor notice exposed 14,200 customer records and cost 38 hours of legal review.</li><li>One team lost nine days of objection rights when notice went to billing inbox.</li><li>Meta's data-transfer breach cost €1,200m in regulatory fines.</li></ul></aside>

Choose by who controls the data path:
- Workato and Power Automate for buyers who contract at enterprise level
- Zapier and Make for teams who confirm the DPA plan first
- Self-hosted n8n or [Activepieces](https://www.activepieces.com) (MIT-licensed core) for teams that want to own the infrastructure

## Workflow Automation DPA Subprocessors and the Short Answer

### What a DPA and a subprocessor list are

The data processing agreement (DPA) is the contract clause set that governs what a vendor may do with the personal data your workflows carry, and what it owes you if something goes wrong.

![A printed data processing agreement, stapled pages with a signature line and paper clips on some clauses, on a desk beside…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/fd67f934-5abf-40b5-84a3-264bd3ee1a00/workflow-automation-dpa-subprocessors-2026-guide-8021f76d.webp)

A subprocessor list names the third parties the vendor hands that data to, such as cloud hosts and email or logging services.

Both matter more than usual in workflow automation, because the platform sees payloads from your CRM, helpdesk and billing tools. **Each new subprocessor widens that path** without anyone on your side signing anything.

### Top workflow automation platforms for DPA terms

Workato and Power Automate suit buyers whose procurement team negotiates a master agreement, since the DPA usually arrives with that contract rather than a checkout page.

Zapier and Make suit teams buying on a card, who should confirm the plan that includes a signed DPA before purchase, not after.

For teams that want to shrink the vendor's footprint, self-hosting n8n or [Activepieces](https://www.activepieces.com), which also ships a fully air-gapped edition, keeps workflow execution on infrastructure you control. It doesn't remove the need to read the vendor's terms for any hosted component.

Where a vendor page doesn't state something, the comparison marks it unconfirmed instead of filling the gap.

### How we checked DPA and subprocessor terms

I judged each platform on the same four checks, using only vendor-owned pages and documents, all read on 2026-11-22; where no page was read, the cell says "Not confirmed":

- Signed DPA, and the plan that includes it
- Public subprocessor list at a stable URL
- Change-notice mechanism for new subprocessors
- Objection clause, and the window to use it

A missing answer on any of the four counts against the vendor, because an unread or unactionable notice is how a routine subprocessor change becomes your incident.

## The 09:14 Notice That Changed a Subprocessor

The platforms differ most in what happens after you sign. What follows is an illustrative scenario, not a report of a real incident: a ten-person finance-ops team runs its customer-data workflow through an automation platform, and the vendor changes who handles that data.

![Two boxes, an invoicing system and a ledger, joined by an arrow carrying a stack of customer billing records, with a small…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/fdb6b9c7-58a7-42fa-a69c-92449e6ebd04/workflow-automation-dpa-subprocessors-2026-guide-7780251f.webp)

### The subprocessor change notice arrives

Every night, the team's workflow moves customer billing records between the invoicing system and the ledger, so the vendor is a processor of personal data and every company it hires is a subprocessor.

At 09:14 on a Tuesday, the vendor emails the account's billing contact to announce one more: a new hosting company that'll store workflow logs.

The message lands in a shared inbox the team treats as a billing mailbox, among renewal receipts, invoice copies and password prompts. It looks like the other unread items around it.

![A finance-ops desk with an inbox open: one vendor notice looks identical to a long column of unread envelopes.](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/e3dee80b-7fd5-4ea7-adc3-bb7a4c62b01e/workflow-automation-dpa-subprocessors-2026-guide-981034b0.webp)

### The subprocessor objection window deadline

Somewhere in the email is a date on which the new subprocessor takes effect, and customers who object must do so before it. That clock runs whether or not anyone has read the message.

The wall calendar marks working days, not this deadline, so nothing in the room counts it down. The window closes with the notice still unopened, which means the team has agreed to the change without deciding to.

### DPA clause on subprocessor objection rights

Weeks later, a customer's security questionnaire asks whether the team approved its processor's subprocessors. Someone opens the data processing agreement (DPA) for the first time since signing and reads the clause on subprocessor changes.

![A workflow builder showing a schedule trigger configured to run every Friday at 3 pm UTC.](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/6cfe18ef-b67b-43f6-b8bc-272af9e74826/elevenlabs-realtime-scribe-v2-pricing-and-featur-b82668c5.webp)

Three things matter in it. First, the vendor commits to notice, but only to the contact address on file, which was the billing mailbox. The team can't claim it was never told.

Second, the right to object depends on a fixed period and a stated reason, so a late objection has no contractual force.

Third, the remedy for an unresolved objection is termination, not a veto. The team could have left; it couldn't have blocked the change.

## Platform Comparison Table: DPA and Subprocessor Terms

In each row below, the same four checks are answered. "Not confirmed" means no vendor page has been read for that cell, so treat it as an open question for the vendor rather than a pass.

| Platform | DPA and plan | Price | Subprocessor list and notice | Self-hosted | Strength | Limit | Best for | Check date |
|---|---|---|---|---|---|---|---|---|
| Zapier | Not confirmed | Not confirmed | Not confirmed | No, cloud service | Broad app catalogue | Plan-level DPA terms unverified | Fast SaaS-to-SaaS automation | 2026-11-22, unverified |
| Make | Not confirmed | Not confirmed | Not confirmed | No, cloud service | Visual scenario design | Notice mechanism unverified | Multi-step data routing | 2026-11-22, unverified |
| n8n | Not confirmed | Not confirmed | Not confirmed | Yes; you then own the hosting subprocessors | Self-hosting control | Cloud terms differ from self-hosted terms | Teams that must keep data in their own environment | 2026-11-22, unverified |
| Workato | Not confirmed | Not confirmed | Not confirmed | No, cloud service | Enterprise governance focus | Price and plan terms unverified | Large integration programmes | 2026-11-22, unverified |
| Power Automate | Covered by Microsoft's customer agreements; plan scope not confirmed | Not confirmed | Not confirmed | No, cloud service | Fits existing Microsoft tenancy | Licensing is bundled, so cost is hard to isolate | Organisations already on Microsoft 365 | 2026-11-22, unverified |
| Activepieces | Not confirmed | Not confirmed | Not confirmed | Not confirmed | Not confirmed | Not confirmed | Not confirmed | 2026-11-22, unverified |

Two readings matter. First, the self-hosted column changes who the subprocessors are: on a self-hosted deployment, the vendor's list stops covering your data path, and your own cloud or hosting provider takes its place.

Second, the check date is the day the cell was last read against a vendor page, so a stale date means the cell can't support a contract decision.

**Accept nothing in the table without the vendor's own document behind it.** The next step is to work out which document, setting or clause settles each unconfirmed cell.

## Tool-by-tool Verdicts on DPA and Subprocessors

Only when its own trust page, signed-form DPA and subprocessor list have been read and dated does a platform count as confirmed on DPA and subprocessor terms. Anything short of that stays unconfirmed.

For Zapier, take the DPA and subprocessor list from its own legal and trust pages, with the retrieval date recorded. Unconfirmed here: whether the DPA is available on every plan or only on negotiated ones, and how the vendor delivers change notices for new subprocessors.

For Make, accept only its own legal documents as a source. Check the notice mechanism for subprocessor additions and whether the DPA writes in objection rights or a web page only describes them. Plan-level availability of the DPA is unconfirmed.

With n8n there are two answers, because it splits into its cloud service and a self-hosted option. For cloud, read the DPA and subprocessor list.

For self-hosted, the vendor processes little of your workflow data, so the subprocessors that matter are the ones you choose for hosting, with their own contracts. Whether a given licence tier changes this is unconfirmed.

### Workato, Power Automate and Activepieces

Because Workato sells mainly through negotiated contracts, the DPA you are shown may differ from the template on its public pages. Ask for the executed version and the current subprocessor list. Price and limits are quote-based, so no list price can be compared.

Rather than a standalone automation DPA, Power Automate's data-protection terms come through Microsoft's broader commercial agreements. The question is which document governs this product and where its subprocessor disclosures sit. Confirm that against Microsoft's own documentation, not a reseller's summary.

Activepieces' connector library holds 750 integrations, counted from its open source monorepo, and roughly 60% of them are community-contributed, so most integrations rely on volunteer maintenance.

That says nothing about data processing. Breadth of connectors is not a contract term.

For the DPA, the same checks apply as for every other vendor on the shortlist. Read its own legal pages, record the date, and confirm what the cloud service discloses.

Because the self-hosted option moves subprocessor risk to your own hosting choices, a cloud-side answer doesn't carry over.

The control side doesn't split the same way, though: the air-gapped self-hosted edition and the managed cloud, including its EU region in Frankfurt, carry the same enterprise controls, so moving the data path in-house doesn't mean buying a thinner product.

The self-hosted docs and the cloud plans list the same set, from SSO and SCIM through custom RBAC, audit logs, release management and secret managers. MoneyGram, Moneypenny, Alan and FundingSocieties run Activepieces in production.

What the current subprocessor list contains and which plans include a DPA remain unconfirmed here.

## Cost of a missed subprocessor change notice

It cost the team four things it can count: review hours, exposed records, days past the objection window, and contract exposure. The figures below are illustrative, set against the scenario above.

### Review hours, exposed records and lost days

| Cost | Unit | Illustrative figure | Who felt it |
|---|---|---|---|
| Review hours | Hours of legal and security work | 38 | Security lead, counsel |
| Records exposed | Customer records reaching the new subprocessor | 14,200 | Customers, support team |
| Days past window | Days after a 30-day objection period closed | 9 | Procurement, which lost its right to object |
| Contract exposure | Customer agreements with flow-down notice duties | 3 | Account owners, finance |

The days figure matters most. Once the window closed, the team could no longer object and could only terminate, so every other line became a cleanup cost rather than a prevention cost.

On a far larger scale, regulators price this failure. [Statista and CNIL](https://www.statista.com/statistics/1403854/eu-data-transfer-gdpr-fines/) put **Meta's transfer fine at €1,200m**, TikTok's at €530m and Uber's at €290m, so transfer penalties reach nine figures.

![Largest GDPR fines tied to transfers and vendor failures](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/2c3734ff-6124-48c2-b2c5-0b4663c7a83b/workflow-automation-dpa-subprocessors-2026-guide-54dffccb.svg "Source: Statista and CNIL")

Vodafone's vendor-related fine was €45m, which means vendor status is no shield against eight-figure exposure.

Closer to this team's size, the processor fines against Dedalus (€1.5m) and Mobius (€1m) are the realistic exposure: small beside Meta's, but larger than any review budget.

### Why the subprocessor change notice went unread

**Nobody owned the notice inbox**. The vendor's change notice went to a shared billing address that the finance team checked for invoices, not for legal changes, so it sat unread past the window.

The second cause came earlier. At purchase, the team compared plan prices and never read the DPA, which would have shown the notice period, the objection mechanism and the termination remedy, and which address to monitor.

Fixing either cause is cheap: assign a named owner to the notice address, and record the DPA's notice terms in the buying file on the day you sign.

## Quarterly DPA and subprocessor checks for vendors

Two habits ended the incident, and both start on Monday: every vendor on the shortlist is checked against the same dated documents, and a named person reads each change notice.

### DPA documents and clauses to request from vendors

The steps below run in order and put the DPA terms, the subprocessor list and the notice channel in one file per vendor.

1. Request the signed DPA, not the template on the trust page. Ask which plan it attaches to.
2. Record the URL of the subprocessor list exactly as the vendor publishes it.
3. Subscribe a shared mailbox to the vendor's change notices, so the notice doesn't depend on one person's inbox.
4. Find the objection clause and write down its window, meaning how long you have to object after a new subprocessor is announced and what happens if you do.
5. Confirm the plan that carries the DPA. If it sits on a higher tier than the one you're buying, the contract doesn't cover you until you upgrade.
6. Assign an owner and a calendar date for the next review.
7. Log the date you checked each item, with the source it came from.

Step four matters most. A window you haven't read is a window that closes on you.

### Assigning a subprocessor review owner and date

Name one person per vendor, not a team, and put the review date in a shared calendar rather than a document. The owner reads each notice when it arrives and compares the subprocessor page against the recorded copy at every review.

On each log entry, carry the vendor, the document, the URL, who checked it and the check date.

## What Activepieces does about this

The problem in this article is a data path that changes without anyone on your side deciding it should. Activepieces answers it mainly by letting you move that path.

The core is MIT-licensed, so you can read what runs, and you can self-host it, including in a fully air-gapped edition.

In that setup the workflow engine is not a vendor-side processor at all, and the subprocessors that matter are the hosting providers you chose and signed with yourself.

A notice can still arrive, but it comes from a contract you hold, about a provider you picked.

Choosing the self-hosted route doesn't mean taking a thinner product. The self-hosted docs and the cloud plans list the same enterprise controls: SSO and SCIM, custom RBAC, audit logs, release management and secret managers.

Audit logs and role limits are what you need to answer a security questionnaire like the one in the scenario above. Teams that would rather not run infrastructure can use the managed cloud, which has an EU region in Frankfurt.

MoneyGram, Moneypenny, Alan and FundingSocieties run Activepieces in production, and they are the references to ask about how they scoped data residency.

We hold ourselves to the same four checks as every other vendor here.

The table row for Activepieces is marked unconfirmed because the DPA plan, the subprocessor list URL, the change-notice channel and the objection window have not been read and dated for this comparison, and a hosting model doesn't settle any of them.

Ask us for the signed DPA and the plan it attaches to, record the date of the cloud subprocessor list, and subscribe a shared mailbox to the notices. If an answer comes back without a document behind it, treat it as open.

## Frequently asked questions

Judged on evidence, a shortlist still leaves four questions that are easiest to settle by asking every vendor in the same words:

- Does the free plan include a DPA, or only paid tiers?
- How fast must the vendor notify you of a breach, and is that window shorter than the deadline you owe your own regulator?
- What does the objection right to a new subprocessor let you do in practice?
- Where is the current subprocessor list published?

Below, the answers say what to expect and what to ask for.

Do I need a DPA with a workflow automation vendor? Yes, if the workflows touch personal data. The vendor then acts as your processor, and GDPR requires a written agreement governing that processing.

A platform that only moves internal, non-personal data is the exception, but most automations pass customer or employee records at some point.

Does self-hosting remove the subprocessor question? No, it moves it. Running the platform on your own infrastructure removes the vendor's hosting from the data path, **but your cloud provider is now your processor**.

Any telemetry, licensing call, AI feature or connected app the workflow reaches is still a third party. Map those, not just the vendor's list.

### Notice periods, plans and the subprocessor list

How much notice must a vendor give before adding a subprocessor? The DPA sets it, and the clause varies by vendor. Some commit to advance notice by email, others only post a change to a web page.

Read the notice period and the delivery channel, then confirm someone on your side is subscribed. The objection right matters only if you see the notice in time, and its remedy is often termination rather than a veto on the vendor's choice.

Is a DPA included on free plans? Not reliably, and this is the check most often skipped. Some vendors make the DPA available to every account, while others tie it to a paid or enterprise tier or require a signed request.

Read the vendor's own DPA page and terms for the plan you'll use, because a free-tier pilot with real data can run without coverage.

Where do I find a vendor's current subprocessor list? Look in the vendor's trust center, security page or legal documentation, and cross-check against the list the DPA references.

Record the date you read it and keep a copy. A list without a visible update date is a weaker control than one that shows when it last changed.

## Related reading

- [EU Hosted Workflow Automation: Best Platforms 2026](https://www.activepieces.com/blog/eu-hosted-workflow-automation-best-platforms-2026)
- [Automation Templates: 6 Platforms Compared (2026)](https://www.activepieces.com/blog/automation-templates-6-platforms-compared-2026)
- [7 Best No Code Automation Platforms Compared for 2026](https://www.activepieces.com/blog/no-code-automation-tools)

## References

- [Statista and CNIL](https://www.statista.com/statistics/1403854/eu-data-transfer-gdpr-fines/)
