How to Update Connected Accounts in Zapier

Reconnect an Existing Account

Use Reconnect when the account itself has not changed, but Zapier needs fresh authorization.

This usually applies after:

• A password reset
• An expired or replaced API token
• A new sign-in requirement
• A multi-factor authentication change
• An administrator policy change affecting the same user account

Open App connections in Zapier. In some accounts, this area may be called My Apps. Find the affected connection, select Reconnect, and sign in to the same app account. Approve the requested permissions, then review the Zaps that use that connection.

Reconnecting refreshes access for Zaps already linked to that account. It does not move a Zap to another user, copy data between accounts, change field mappings, or alter workflow logic.

Add a New Connection for a Different Account

Create a separate connection when the Zap needs access to a different account or workspace.

Common examples include:

• Moving an automation from one employee to another
• Connecting a client’s account instead of an internal account
• Replacing a personal account with a company-managed account
• Moving work from a sandbox environment to production
• Using a different CRM, inbox, store, or project workspace

Adding a connection does not automatically replace the old one inside existing Zaps. Open each affected Zap and select the new account in every trigger, action, search, lookup, and other app step that uses the old connection.

One Zap can use different accounts at different points. For example, its trigger may use one workspace, a lookup step may use another, and an action may send data through a third account. Review every app step individually.

Reconnect or Replace?

A reconnect can affect every Zap attached to that connection. Replacing an account inside a single Zap is more contained, but requires more editing. This distinction matters when automations send email, create invoices, update customer records, move files, or post notifications.

Move a Zap to a Different Connected Account

Use this process when the workflow needs another person, client workspace, business account, or environment.

1. Add the new app connection in Zapier.
2. Open each Zap that uses the old account.
3. Start with the trigger and select the new account where needed.
4. Open every action, lookup, search, and other app step.
5. Replace the old account selection with the new connection.
6. Review selected folders, channels, pipelines, calendars, spreadsheets, databases, and other dropdown values.
7. Review field mappings, filters, and Paths.
8. Save or publish the updated Zap.
9. Run one controlled record through the full workflow.
10. Keep the old connection until the result succeeds in the intended destination.

A successful sign-in does not mean the workflow is ready. The new account may not have access to the same folders, records, fields, users, or destinations as the old one.

Review Settings That Belong to the Old Account

A new connection can work while the Zap still points to settings from the previous account. This is common when moving between workspaces that use different names, permissions, or structures.

Review these items after changing accounts:

• Pipelines, stages, and record owners in a CRM
• Folders, shared drives, and spreadsheets
• Calendars and mailboxes
• Channels and users in a messaging app
• Custom fields and field formats
• Filters and Paths that depend on source data
• Templates, databases, and project boards

For example, a Zap may connect to a new CRM workspace but still reference a pipeline that does not exist there. A connection change alone will not repair that setup. Update the affected selections and mappings before using the workflow for live records.

If the new account uses a substantially different data model, duplicate the Zap and revise the duplicate before changing the live workflow. A store with different shipping fields, a CRM with renamed deal stages, or a project workspace with different templates may require workflow changes rather than a simple account swap.

Test the Full Workflow

After updating an account, run a controlled record through the entire Zap. An individual action test can show that one step can complete a request, but it does not show whether the trigger, filters, Paths, mappings, and downstream actions work together.

Use a record that resembles a normal live item and includes the fields used later in the Zap. Then confirm that:

• The trigger receives the record from the intended account.
• Filters and Paths allow it through as expected.
• Each action uses the intended account.
• The result appears in the correct CRM, inbox, folder, calendar, spreadsheet, or other destination.
• Task history does not show authorization or permission errors after the next live run.

Turn the Zap off during the change when an incorrect run could send customer email, create financial records, or update sensitive data in the wrong workspace.

Use Shared Connections Carefully

A shared connection can be useful when one approved account should run several related Zaps. It also means that a password reset, permission change, or revoked token can affect every workflow using that account.

Use a shared connection when the same account should own the work across those Zaps. Keep separate connections for:

• Different clients or business entities
• Production and sandbox systems
• Personal and company-managed accounts
• Departments with separate data permissions
• Workflows with different approval or audit boundaries

For team-owned automations, use a company-managed account rather than one employee’s personal account. Personal access can cause disruption when that person changes roles, resets a password, or leaves the organization.

Avoid repeatedly switching a single connection between clients or business units. Separate connections make it easier to see which account is responsible for each workflow and reduce the chance of sending data under the wrong account.

When Reconnecting Is Not the Fix

Reconnect or replace a connection only when the problem is related to account access. Use a different method when the issue comes from:

• Broken field mappings
• Missing source data
• Changed workflow logic
• App-side restrictions
• Permissions for a particular folder, object, or field
• A data model that no longer matches the Zap

Update ownership, shared mailbox access, folder permissions, and similar settings in the connected app’s administration tools first. Then reconnect Zapier through an account that has the approved access.

Ask the app administrator for help when single sign-on, IP restrictions, API controls, or organization-level approval prevents a connection. Repeated reconnect attempts will not override an access policy.

Before Removing the Old Connection

• Identify every Zap using the existing connection.
• Decide whether the change is a credential refresh or a different account.
• Add the replacement connection before editing live workflows.
• Update every affected trigger, action, lookup, search, and other app step.
• Review dropdown selections, field mappings, filters, and Paths.
• Run a controlled record through the complete workflow.
• Confirm the result appears in the intended destination account.
• Review task history after a live run.
• Remove unused access only after the transition is complete.

FAQ

How do I reconnect an expired account in Zapier?

Open App connections or My Apps, select the affected account, and choose Reconnect. Sign in to the same account, approve the requested permissions, and run a controlled workflow record through the Zaps that use that connection.

Does reconnecting an account update every Zap?

Reconnecting refreshes authorization for every Zap linked to that specific connection. It does not switch those Zaps to a different app account. To use another account, add a separate connection and select it inside each affected Zap step.

Why does a Zapier test succeed while the live Zap fails?

An action test confirms that one selected account can complete one request. A live run can still fail when a filter blocks the record, a required field is missing, a selected folder or pipeline is unavailable, or the account lacks permission for a particular item.

How often should connected accounts be reviewed?

Review critical connections every three months and after password resets, employee departures, administrator changes, permission changes, or app security-policy updates. Investigate authorization and permission errors as soon as they appear.