How to Deploy Another Version of a Function in Zapier

When you update a custom function in Zapier, you often need a safe way to promote that new version to production without breaking existing workflows. This guide explains how to deploy another version of a function, how versioning works, and what to consider before you switch which version is live.

Understanding Function Versioning in Zapier

Functions in Zapier are versioned so you can test changes and deploy them carefully. Each function has:

• A unique function name.
• One or more versions associated with that function name.
• One version that is marked as the live version at any time.

When a function is used in a Zap or another automation, Zapier calls the current live version of that function. Changing which version is live does not change the function name; it only changes which code runs behind that name.

Before You Deploy a New Function Version in Zapier

Before you deploy another version of a function in Zapier, review these preparation steps:

• Confirm tests pass: Make sure the new version has been tested thoroughly with expected and edge-case inputs.
• Review dependencies: Check whether other functions, Zaps, or apps depend on outputs from the function you are about to update.
• Plan timing: Deploy during a low-traffic period if your function is used in time-sensitive workflows.
• Document changes: Note what changed between versions, such as parameters, return schema, or error handling.

Having a clear understanding of the change helps you avoid unexpected issues once the new version is deployed live in Zapier.

How to Deploy Another Version of a Function in Zapier

The deployment process in Zapier promotes an existing version of a function so it becomes the live version. The general workflow is:

1. Create or edit a version of the function.
2. Test and validate the new version.
3. Mark the updated version as live.

Step 1: Open the Function in Zapier

Start by navigating to the function you want to update in your Zapier environment. In the functions listing, locate the function name that already exists. Each function entry typically displays:

• The function name or identifier.
• The current live version label.
• A way to open the function details and version history.

Select the function to open its details page and review available versions.

Step 2: Review Existing Versions in Zapier

On the function details screen, you should see each version that has been created under that function name. For each version, there will usually be:

• A version number or ID.
• Metadata such as who last edited it and when.
• An indication of which version is currently live.

Identifying the correct version is critical. Ensure you are selecting the version that contains the updated logic you intend to promote in Zapier.

Step 3: Verify and Test the Target Version

Before you deploy another version of a function, verify that it behaves as expected:

• Run sample inputs and check that outputs match your requirements.
• Verify any new fields, parameters, or headers you added.
• Confirm error messages are clear and helpful.

If your function is used by multiple Zaps or other functions, consider running tests that simulate those calling patterns. The more confident you are before the version goes live in Zapier, the smoother the transition will be.

Step 4: Deploy the New Version in Zapier

Once you have identified and tested the correct version, you can deploy it. In the function version list, there will be an action to promote or deploy a version. Use that action to mark this version as the latest live version for the function name.

After you deploy:

• All future calls to this function in Zapier will use the newly deployed version.
• The function name does not change; only the backing version changes.
• Previous versions remain in history but are no longer used for new executions.

How Live Function Versions Work in Zapier

Zapier maintains a single live version per function name. Understanding how live versions behave helps you plan updates and rollbacks.

What Happens When You Change the Live Version

When you deploy another version as live in Zapier:

• New runs of any Zap that calls the function will use the new live version.
• Existing historical runs are unaffected; they keep the results they already produced.
• If the function output structure changed, dependent Zaps may need updating.

Because of this, treat each deployment as a controlled change, and follow your normal release checklist before updating the live version.

Managing Backward Compatibility in Zapier

To minimize disruption when you change which function version is live in Zapier, aim for backward-compatible updates:

• Preserve existing input parameters where possible.
• Add new fields instead of renaming or removing old ones.
• Maintain consistent data types for existing fields.
• Log additional data in a way that does not break current consumers.

If you must introduce a breaking change, consider coordinating updates across any Zaps or tools that depend on the function.

Rolling Back a Function Version in Zapier

If the newly deployed version causes issues, you can roll back by making a previous version live again in Zapier.

1. Open the function in the functions listing.
2. Locate the earlier version that you want to restore.
3. Use the deploy or promote action to set that earlier version as live again.

Rolling back restores the behavior of the older version for all new calls to that function. This is especially useful if you quickly discover problems after deploying another version in Zapier.

Best Practices for Safe Function Deployments in Zapier

To keep your automation stable while you deploy new function versions in Zapier, follow these best practices:

• Use clear version notes: Add short descriptions of what changed in each version.
• Deploy gradually: If possible, test first with non-critical Zaps before rolling changes to important workflows.
• Monitor logs: After deployment, watch function logs or run history for unexpected errors or timeouts.
• Coordinate with your team: Inform teammates when you promote a new version, especially if they maintain related Zaps.

More Resources About Zapier Functions

For the official reference on how to deploy another version of a function in Zapier, including any new interface updates or limitations, review the original help article: Zapier help: How to deploy another version of a function.

If you need expert help building or optimizing automations around Zapier, you can also explore consulting resources such as Consultevo for strategy, implementation, and troubleshooting support.

By understanding how function versioning works and following a structured deployment process, you can confidently deploy another version of a function in Zapier while keeping your existing automation stable and reliable.

Need Help With Zapier?

Work with ConsultEvo — a

Zapier Certified Solution Partner

helping teams build reliable, scalable automations that actually move the business forward.

Get Zapier Help