Webhook migration guide

Webhooks will be sunset on Jan 15, 2026. Any existing flow modules that use webhooks will stop running after this date. You can preserve these modules’ functionality by migrating them to actions, a more powerful, cloud-based alternative to webhooks. This guide shows how to migrate your workflows to actions.

Benefits of migrating webhooks to actions

Actions provide everything webhooks offered, plus the following:

• Cloud deployment - Your flows run reliably as deployed actions in the cloud in addition to running locally in the Postman cloud runtime environment.

• Built-in scheduling - Run actions automatically at custom intervals with scheduled flows.

• Better observability - Track run history, logs, and performance metrics in analytics.

• Version control - Snapshot and manage different versions of your workflows.

Differences between webhooks and actions

Feature	Webhooks	Actions
Execution	Local	Cloud-based
Scheduling	Required external monitors	Built-in scheduled flows
Observability	Limited	Full run logs
Versioning	None	Snapshots & deployment tracking
Reliability	Depends on local setup	Production infrastructure

Migration process

To migrate your webhook-based flow module to an action, do the following:

Step 1 - Copy your webhook test data

1. Open your webhook-based flow module.

2. Click Preview.

3. Copy the JSON body from the preview and close the preview pane.

Step 2 - Create a new action

1. Click Create a new folder or flow and select Create action.

   

2. Click and delete the default AI Agent and Display blocks.

Step 3 - Set up your request trigger

1. In the right sidebar, click Scenarios.

2. Hover over the Request Trigger default scenario and click Edit.

3. Paste the JSON body from your webhook into the scenario.

4. Save and close the scenario pane.

Step 4 - Copy your flow logic

1. In your webhook-based flow, press ⌘ + A or Ctrl + A to select all the blocks.

2. Copy the blocks.

3. In your action, paste the blocks onto the canvas.

Step 5 - Connect the blocks

1. Connect the Request block’s Body port to your first flow block.

2. Connect your final block to the Body port of the Response block.

3. Make sure all blocks are correctly connected.

Step 6 - Test your action

1. Click Run to run the scenario manually.

2. Verify everything works as expected.

3. Check the run logs for any errors.

Step 7 - Deploy to the cloud

1. In your action, click Deploy in the upper right corner.

2. Enter an Action URL.

3. Click Deploy. Your action is live and available at the URL you specified.