SaaS Automation Security: Credentials, Webhooks and SOC 2
By Rowan Ellis · Updated October 7, 2026
How to secure SaaS automations: credential storage, OAuth scopes, webhook signatures, SSO and audit-log plan gates, data residency, and SOC 2 evidence.
Securing a SaaS automation comes down to six checks: where the tool stores your credentials, how narrow the permissions you granted it are, whether your webhook endpoints verify who is calling, which plan you need for SSO and audit logs, where the data is stored, and whether the vendor's SOC 2 claim is backed by a report you can read. This guide takes each in turn and uses what Make, Zapier, n8n, HubSpot and Customer.io state on their own security pages. Where a vendor page is silent, that is flagged as a question to ask rather than filled with an assumption.
1. Where your credentials live
Every automation holds keys to other systems: a billing API key, a CRM token, an email-sending key. The security of the workflow tool is the security of all of them at once.
What the vendors say. Make's security page states that passwords are stored in an encrypted format that cannot be reproduced by anyone, including Make employees, with AES-256 full-disk encryption and AWS Key Management Service for keys, and TLS 1.2 and 1.3 for connections to third-party services. For n8n, the encryption key rotation guide describes a two-layer model: an instance encryption key set at deployment, and a data encryption key that directly encrypts credentials and OAuth tokens. Rotation is a self-hosted feature, not available on n8n Cloud, and the guide calls enabling it a one-way change that needs a full database backup first and the same N8N_ENCRYPTION_KEY on every main and worker instance. n8n's pricing page lists an external secret store integration under Enterprise.
What you control. Keep one connection per workflow purpose rather than one master connection reused everywhere, use a service account instead of a person's login, and record where each key was created so you can revoke it. If a tool stores executions, remember the data in them: n8n's execution data redaction exists because workflow runs can contain personal data and authentication tokens, and the docs list it as an Enterprise feature for self-hosted instances. On Make, execution logs are kept for 30 days by default and longer on Enterprise, per its security page, so what passes through a scenario also sits in its log for that long.
2. Scopes: grant the narrowest OAuth permission that works
When you click "connect" and approve a scope list, you hand the workflow tool a token that works until someone revokes it. The HubSpot Trust Center shows two different ways such tokens end up exposed, both from 2026 announcements:
- On July 9, 2026 HubSpot described a vulnerability in its WordPress plugin (CVE-2026-57736) in which authenticated WordPress users with contributor-level access or above could retrieve the site's plaintext HubSpot OAuth refresh token. HubSpot said it had no evidence of exploitation in the wild and fixed it in plugin version 11.3.61.
- On May 28, 2026 HubSpot described rotating OAuth tokens and API keys for apps that used the integration platform Composio, after Composio disclosed unauthorized access to some of its internal systems. HubSpot stated the issue did not stem from a vulnerability in the core HubSpot platform, and on June 3 reported no evidence that HubSpot customer accounts were compromised.
The practical reading is that a token can leak from a plugin or from a connector layer you do not run, so the damage depends on what the token was allowed to do. Before approving a connection, read the scope list and ask whether the workflow needs to write at all. A workflow that reads new deals to post an alert needs read access to deals, not admin access to the account. Prefer a connection owned by a dedicated automation user with a narrow role, and write down which workflows use it so that a rotation, like the one HubSpot performed in the Composio case, does not take down something you did not know depended on it. HubSpot's own notice says super admins see a banner on the Connected Apps page and can re-enable connections with new credentials, so know who your super admins are.
3. Webhooks: verify the signature before acting
Billing and product events usually reach your workflow as an HTTP request to a public URL. Anyone who learns the URL can send a request that looks like an event. Stripe's webhook documentation is explicit: without verification, an attacker could send fake events to trigger actions such as fulfilling orders, granting account access or modifying records. What it describes, and what any workflow that acts on a Stripe event should do:
- Verify the
Stripe-Signatureheader against the endpoint'swhsec_signing secret, using Stripe's official libraries or its documented manual method. - Use the raw request body. Stripe says any manipulation of the raw body, including by a framework, makes verification fail.
- Reject stale requests. The signature includes a timestamp, and Stripe's libraries default to a tolerance of five minutes, which is how it mitigates replay attacks.
- Treat secrets as per endpoint and per mode. Each endpoint has its own secret, and test and live keys have different ones.
- Roll the secret periodically or when it may be compromised. Stripe lets you expire the old secret immediately or keep it valid for up to 24 hours while you update your code.
The question for a no-code tool is whether its webhook trigger can do the signature step. Ask the vendor for the documented way to verify an incoming signature, and if there is none, put a small endpoint you control in front that verifies and then forwards a clean event. Do not paste a signing secret into a field that is logged or shared in plain text. Stripe's guide has code for each language; use that code, not a rewritten version, and keep the endpoint returning a 2xx quickly, as the guide advises.
4. SSO, roles and audit logs: which plan unlocks them
Identity controls are the most common reason a team is pushed up a plan. What each vendor's own pages tie to which tier:
| Tool | Identity and governance features, as stated | Plan and list price |
|---|---|---|
| Zapier | Team lists SAML SSO and shared connections; Enterprise lists advanced admin permissions, custom data retention and observability | Team from $69/month; Enterprise contact for pricing |
| n8n | Pro lists admin roles; Business lists SSO and LDAP; Enterprise lists external secret store, log streaming and extended data retention | Pro $50/month and Business $800/month, both billed annually; Enterprise contact sales |
| Make | Security page: SSO sign-in with Google, Facebook and GitHub; Enterprise customers can use their own SSO; Pricing page lists advanced security features under Enterprise | Enterprise custom pricing (pricing) |
| Pipedrive | Ultimate lists account security rules and alerts | US$79 per seat per month billed annually |
Do the sum before you assume SSO is a small upgrade. On n8n, the step from Pro at $50 a month to Business at $800 a month is $750 a month, or $9,000 a year, for a plan that also lists 40K executions, six shared projects and a self-hosted-only deployment. On Zapier, Team starts at $69 against Professional's $19.99, a difference of $49.01 a month. On Pipedrive, a ten-seat team moving from Premium to Ultimate for security rules pays 10 x ($79 - $59) = $200 more each month. Whether those numbers are worth paying depends on whether your customers' security reviews require SSO, not on whether it is on the list.
Audit logs and retention are the other gate. Zapier's MCP security page says events appear in the account's overall audit log and that Enterprise accounts support configurable data retention. n8n lists log streaming under Enterprise. Make's pricing page names audit logs among its features; ask Make which plan includes them before you rely on them in a security questionnaire.
5. Data residency: where the data sits
Residency is a plain factual question, and the vendors answer it differently:
- Zapier. Its MCP security page states that customer data is stored in AWS US-East 1 in the United States, and that region-specific data residency is not available unless otherwise agreed.
- Make. Its security page says the infrastructure runs on AWS private instances in a cluster deployed over two zones, and its pricing page names AWS in the EU and North America as hosting. Enterprise runs in a separately managed AWS environment isolated from the self-service cloud.
- Customer.io. Its security page says its regional infrastructure ensures EU data residency and that the platform supports data rectification, the right to be forgotten and an audit trail for GDPR.
- n8n. The docs linked above cover securing a self-hosted instance, where you pick the infrastructure and so the region. The key rotation guide notes that rotation is not available on n8n Cloud, so a Cloud customer should ask n8n where its data is hosted and which controls apply.
If your customers are in the EU and your contract promises EU-only processing, a workflow that copies customer records through a US-hosted connector can break that promise even when every other system is compliant. Map the path of one customer record through the whole workflow, including logs and the AI steps some tools now add, before you sign the data processing agreement. Subprocessors matter here too: on September 5, 2026 Zapier's Trust Center announced Meta as a new AI-provider subprocessor, available as an optional model in AI by Zapier and, for Enterprise accounts, enabled only by a company administrator.
6. SOC 2: the report is the evidence, the badge is the claim
Every vendor above shows a compliance badge row. A badge says the vendor claims a framework. The report says what an auditor tested and over what period. Here is what each page actually offers a buyer:
| Vendor | What the page states | What you can ask for |
|---|---|---|
| Zapier | Trust Center lists SOC 2 Type II, SOC 3, GDPR and CCPA badges. An August 3, 2026 announcement says the SOC 2 Type II and SOC 3 reports cover June 1, 2025 through May 31, 2026. | Per its help article: SOC 2 report, SOC 3, pen-test results, whitepaper and policies; some need an NDA signed in the Trust Center. |
| HubSpot | Trust Center lists SOC 1 Type II, SOC 2 Type II, SOC 3, HIPAA, GDPR, CCPA, EU Cloud Code of Conduct and TRUSTe badges, with 42 documents. A June 23, 2026 notice announces its first SOC 1 report and updated SOC 2 and SOC 3 reports. | Annual third-party pen-test report, subprocessor list, disaster recovery plan, vulnerability disclosure program. |
| Make | GDPR adherence plus completed SOC 2 Type II and SOC 3 audits; the information security program is ISO 27001 certified. | SOC 3 as the public summary; the SOC 2 report details internal controls. A whitepaper is linked. |
| Customer.io | States the platform is HIPAA compliant and SOC 2 Type II certified, and shows GDPR, CCPA, ISO 27001, AICPA SOC and HIPAA badges. | The page gives a legal contact address; ask for the report and its period. |
Three things to do with that. First, read the period: a report that ended 18 months ago says little about today, and Zapier's help article notes the SOC 2 Type II audit is conducted annually with updated reports published after each cycle. Second, read scope and exceptions in the full SOC 2 report, not just the headline, and note that Zapier's August announcement lists security, availability, confidentiality and privacy among the controls covered. Third, remember what SOC 2 certifies: the vendor's own controls. It does not certify how you configured your workflows, who has access to your connections, or whether your webhook verifies signatures. Those remain your job.
Subscribe to the vendor's trust center updates if it offers them. Zapier's Trust Center says you can subscribe for subprocessor changes, and the September 2026 change above is the kind of event your own customers' vendor reviews may ask you to report on. Industry rules such as HIPAA are a separate question from SOC 2: Customer.io and HubSpot state HIPAA compliance, but whether a given workflow can carry health data is a contract question, so ask each vendor in writing what agreement and plan they require before any protected data flows through it.
What to do when a connected vendor has an incident
The two HubSpot notices above are a useful rehearsal. In the Composio case the customers who were affected were told by Composio or HubSpot directly, a banner appeared on the Connected Apps page, and the remedy was to re-enable the connection with new credentials. A team that had written down which workflows use which connection could do that in minutes; a team that had not had to discover broken workflows one by one. Keep a short register: connection name, owning workflow, scopes granted, who can revoke it, and where the vendor posts incident notices. Subscribe to those notices.
Questions teams ask when they review automation security
Is self-hosted n8n more secure than a cloud connector?
It gives you more control, and more to do. n8n's security overview lists the work for a self-hosted instance: security audits, SSL, SSO configuration, encryption key rotation, hardening task runners, redacting execution data, disabling the public API, blocking nodes and SSRF protection. A cloud vendor's SOC 2 report covers its controls; on self-hosted n8n those controls are yours to implement and evidence.
Does a SOC 2 badge mean my workflow is compliant?
No. It describes the vendor's controls over a period. Your own responsibilities, such as scopes, who holds connections, and webhook verification, are outside it.
What should I look at first in a small team?
Start with the connection register and the webhook endpoints that act on money or access, since those combine the biggest impact with the cheapest fixes. Then check whether any customer contract requires SSO or EU-only processing, because that decides whether a plan upgrade is unavoidable. The automation mistakes guide covers the duplicate-delivery and silent-failure problems that sit next to these.
Comparing automation tools?
See each tool's billing unit and list price alongside its plan tiers.
View All Automation Tools