Ruvix

Publishing ​

Publishing a workflow creates a live version that can be triggered automatically by webhooks, cron schedules, and DataStore triggers.

How Publishing Works ​

  1. Open your workflow in the builder
  2. Make sure your working version is configured and tested
  3. Click the "Publish" button in the toolbar
  4. A snapshot of your working version becomes the new published version

The published version is what runs when:

  • An external service sends a request to your webhook URL
  • A cron schedule fires at the configured time
  • A DataStore trigger detects a table change

Manual Runs vs Published Version ​

  • Manual runs (clicking "Run" in the builder) always use the working version
  • Automated triggers (webhook, cron, DataStore) always use the published version

This separation lets you test changes in the working version without affecting live automated workflows.

Webhook URLs ​

When you publish a workflow that has a Webhook trigger node, a unique webhook URL is generated:

GET/POST https://your-domain/api/webhook/{token}/{slug}/

This URL is displayed in the workflow builder after publishing. External services can send requests to this URL to trigger the workflow.

TIP

Webhook URLs remain stable across publishes — updating your workflow doesn't change the URL.

Unpublishing ​

There is no explicit unpublish action. To stop automated triggers from running:

  • Webhooks: Remove the URL from the calling service
  • Cron: Delete or disable the cron trigger node
  • DataStore triggers: Remove the trigger node from the workflow