Skip to content

Deploying Automations

Now that our automation is complete, it's time to save it and choose how it should run. To save, simply enter a name for your automation and click the Save button in the toolbar at the top of the editor. Once saved, the page will navigate to the Automations page, where you'll see your newly listed automation.

Monkedo distinguishes between testing or running once and going live in the background:

Action

When to use

What happens

Run (Automations page)

Manual or Schedule triggers only

Executes the current version once from the Automations list. Does not require deploy.

Deploy

Webhook, email, app event, and other background triggers

Publishes the automation so triggers and schedules run automatically without manual intervention.

Run Without Deploy

Automations with a Manual Trigger or Schedule Trigger can be run directly from the Automations page using the Run button, even if they have never been deployed. This is useful for one-off tests or scheduled jobs you trigger manually.

If a deployed version already exists and differs from your latest edits, Monkedo asks whether you want to run the latest (editable) version before proceeding.

Deploy for Background Execution

For automations that should react to external events — incoming webhooks, new emails, app triggers, and similar — you must deploy the automation. Until deployment, those triggers are not active in the background.

After deployment, a Schedule Trigger also runs automatically at the configured times without using the Run button.

When you save an automation, it doesn't start running in the background right away. This gives you time to review and make any final adjustments. Once you're ready for it to go live, click the Deploy button on the Automations page.

After deployment:

  • Schedule, Webhook, Email, and app event triggers listen for events automatically.

  • You can still use Run on Manual and Schedule automations for ad-hoc execution.

If you need to temporarily stop an automation, you can pause it using the Pause button, which becomes visible after deployment. When paused, the automation won't respond to any triggers or scheduled events. You can resume it later by redeploying it, allowing it to start running again.

Note: You can only pause an automation that has been deployed at least once.

Pause button

Even after deploying an automation, you can still make changes if necessary. To avoid disrupting the live automation, any modifications you make won't take effect immediately. Once you've made changes, simply click the Re-deploy button. This button appears only after you've edited a deployed automation, ensuring the updates are applied when you're ready.

Re-deploy button

Congratulations on completing this tutorial! 🎉 You've successfully built an automation that schedules and posts tweets to X (formerly Twitter). Along the way, we explored many of Monkedo's powerful features, including setting triggers, working with tables, using named values, controlling automation flow, and creating expressions. With these skills, you're now equipped to create automations for a wide variety of tasks across different apps and services.

While we covered a lot in this tutorial, Monkedo offers many more useful features, from advanced data processing to deeper integrations with hundreds of apps. Whether you want to create complex workflows or streamline simple tasks, Monkedo provides the flexibility and tools you need. Be sure to check out our documentation to discover more capabilities and continue expanding your automations.

Thank you for following along, and happy automating! 🚀