Zapier: Connection errors affecting Salesforce Pardot Zaps
Affected components: Polling Triggers
Timeline of updates
- investigating
Some customers using the Salesforce Pardot integration are experiencing connection errors that prevent their Zaps from running. Other Pardot connections continue to run normally. We are investigating the ongoing errors and checking recovery of affected connections and delayed Zap runs.
If you need any assistance in the meantime, please contact our support team here "here": https://zapier.com/app/get-help (opens in new tab).
- investigating
We have confirmed that this is an upstream issue with the Pardot service and are monitoring its status. There is no confirmed recovery time yet.
We are assessing whether any trigger activity was missed during the disruption and whether additional recovery steps will be needed.
Once connections recover, we will verify that affected Zaps resume and check whether delayed or held runs need additional attention. We will let you know if any action is required from your team.
If you need assistance in the meantime, please contact our support team "contact our support team": https://zapier.com/app/get-help (opens in new tab).
- investigating
Reconnecting your Salesforce Pardot account in Zapier may resolve the connection errors. We have observed recovery for a small number of customers who appear to have reconnected their accounts, but have not yet confirmed that this works for everyone affected.
If you are still experiencing errors, try reconnecting your Pardot account. If errors persist or you need help, please contact our support team "contact our support team": https://zapier.com/app/get-help (opens in new tab). We are continuing to work with Salesforce on the underlying issue.
- investigating
We're continuing to investigate the Salesforce Pardot connection errors and are working with Salesforce to identify the underlying cause.
Reconnecting your Pardot account in Zapier may resolve the errors. We've seen recovery for a small number of customers who reconnected, but we haven't confirmed that this works for everyone affected.
If you're still seeing errors after reconnecting, or you need help, please contact our support team. "contact our support team.": https://zapier.com/app/get-help (opens in new tab)
Thank you for your patience, and we'll share another update as soon as we have more information.
Changes Rewindex caught on this incident
- Major incident: Connection errors affecting Salesforce Pardot Zaps
- Incident updated: Connection errors affecting Salesforce Pardot Zaps
- Incident updated: Connection errors affecting Salesforce Pardot Zaps
- Incident updated: Connection errors affecting Salesforce Pardot Zaps
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
ceffaf2022a2f971…Version 2 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
372e3a77f6b7e8d4…Version 3 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d165d0df29315ded…Version 4 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
9dc882392eb464c6…
Impact, status and times are the vendor’s own, as last archived. View on status.zapier.com (opens in new tab).