Deploy a pattern

Deploying a pattern makes it live. Once deployed, the pattern responds to its trigger — whether that is a webhook request, a cron schedule, or a call from another pattern. This guide covers the full deployment lifecycle: deploying, monitoring, redeploying, pausing, and undeploying.

Before you begin

Make sure you have:

• A pattern that is ready to deploy (built and tested in the editor)
• Verified the pattern works using the Test button in the editor toolbar

If you have not built a pattern yet, start with the Your first pattern guide.

Deploy from the editor

1. Open your pattern in the visual editor.
2. Select Deploy in the toolbar.
3. DRAGOPS compiles the pattern and pushes it to the execution engine. This takes a few seconds.
4. When deployment completes, the toolbar shows a green status indicator and the deployment details appear in the panel.

For patterns with a webhook trigger, the deployment panel displays the webhook URL. Copy this URL and register it with your external service (GitHub, Slack, Stripe, or any HTTP-based integration).

View deployment status

The Deployments page provides an overview of all your active deployments.

1. Go to the Deployments page from the main navigation.
2. Each row shows the pattern name, deployment status, trigger type, and when it was last deployed.
3. Select a deployment to open the detail page.

The deployment detail page shows the full configuration, webhook URL (if applicable), and the execution history for that deployment.

Monitor executions

Every time a deployed pattern runs, DRAGOPS records an execution with a timestamp, status, and node-by-node log.

1. Go to the deployment detail page.
2. The Executions section lists every execution in reverse chronological order.
3. Select an execution to view the full log.

The execution log shows:

• Status — Success or failure
• Duration — How long the execution took
• Node log — Each node that ran, in order, with timestamps and output values
• Error details — If the execution failed, the log highlights the node that caused the failure and displays the error message

Use the execution log to verify your pattern works correctly with real data, diagnose failures, and understand timing.

Pause and resume a deployment

Pausing a deployment temporarily stops the pattern from executing without removing it.

To pause:

1. Go to the deployment detail page.
2. Select Pause.
3. The deployment status changes to "Paused". Incoming webhooks return a 503 response, and scheduled triggers do not fire.

To resume:

1. Go to the paused deployment's detail page.
2. Select Resume.
3. The deployment returns to active status and begins accepting triggers again.

Pausing is useful when you need to temporarily stop a pattern — for example, during maintenance on an external service that the pattern depends on.

Redeploy after changes

When you edit a pattern and want the changes to go live, redeploy it.

1. Open the pattern in the visual editor.
2. Make your changes (add nodes, change wires, update properties).
3. Test the updated pattern using the Test button.
4. Select Deploy in the toolbar.

DRAGOPS deploys the new version of the pattern. The previous version stops and the new version takes over. There is no downtime during redeployment — the transition is seamless.

Each deployment creates a new version. You can see the version history on the deployment detail page.

Undeploy a pattern

Undeploying stops a deployment entirely and removes it from the active deployments list.

1. Go to the deployment detail page.
2. Select Undeploy.
3. Confirm the action.

The pattern returns to draft status. It no longer responds to triggers, and its executions stop.

Webhook URLs survive undeploy

If your pattern uses a webhook trigger, the webhook URL is permanently assigned to the pattern. It does not change when you undeploy and redeploy. This means you can safely register the URL with external services — it remains valid across the full deployment lifecycle.

When a pattern is undeployed, requests to its webhook URL return a 404 response. When you redeploy, the same URL becomes active again.

Verify the result

After deploying, confirm everything works end to end:

1. For webhook-triggered patterns — Send a test request to the webhook URL and check the execution log on the deployment detail page.
2. For scheduled patterns — Wait for the next scheduled execution and verify it appears in the execution history.
3. For callable patterns — Execute the parent pattern that calls this one and verify both executions complete successfully.

Review the execution log to confirm each node ran as expected and the output values are correct.

What is next?