Quickstart: Workflow Builder

Written By Luke Wakefield

Last updated About 12 hours ago

Introducing a new way to build Workflows, Integrations and Automations in Siteglide!

Workflow Builder is a no-code tool that lets you visually build out workflows, integrations and automations without needing to code.

Read the Release Notes: Workflow Builder

Powered by Latenode

We have partnered with Latenode to offer their powerful yet affordable Workflow Automation Builder right inside Siteglide fully integrated with the Siteglide Site API meaning you can run Siteglide Triggers and Actions (we’ll keep adding more endpoints, just request them on our Roadmap).

For more information and guides on Latenote itself please visit: https://latenode.com/

Usage

Workflow Builder works in the same way as all other Siteglide features, you only pay for what you use billed as Siteglide Units which equal 1 Latenode Credit (see breakdown below).

How Latenode Pricing Works

We charge for time, not tasks.

Most platforms count every node and operation. A 4-node workflow counts as 4 operations. Run it 25,000 times and you've used 100,000 operations—hitting expensive pricing tiers.

Latenode counts processing seconds instead. That same 4-node workflow might take 5 seconds to run. You pay for 5 seconds, regardless of how many nodes it contains.

How Credits Work

1 credit equals	30 sec
Min charge per run	0.1 credit (3 sec)
Max runs per credit	10
1 Latenode Credit equals	1 Siteglide Unit

Specific Limits/Details

CPU Credits? 1 credit = 30 seconds of execution time.	1
Max Workflow Executions? Total times all your scenarios can run per month. 1 execution = 1 complete scenario run, regardless of how many nodes it contains.	10
Active Scenarios? How many scenarios can be enabled and ready to trigger at once. You're never forced to disable one automation to activate another on paid tiers.	∞
Nodes per Scenario? Maximum steps in a single workflow. Unlimited — add as many conditions, integrations, and logic branches as needed without extra cost.	∞
Connected Accounts? Saved third-party service authorizations (e.g. one Gmail account, one Slack workspace). Each unique service login counts as one connected account slot.	100
Parallel Executions? How many scenarios can run at the exact same time. If you hit the limit, extra triggers queue and wait — critical for high-traffic webhooks or frequent scheduled runs.	20
AI Copilot Requests? Monthly uses of the built-in AI assistant that writes and debugs code inside your scenarios. Each natural-language prompt to the AI consumes one request.	500
Trigger Interval? Minimum time between checks for polling-based triggers (e.g. 'new email in Gmail'). Webhook-based triggers are always instant regardless of this setting.	1 min
Max Scenario Runtime? The longest a single workflow run can take before it's automatically stopped. Longer limits are needed for batch processing, web scraping, or sequences with API rate-limit delays.	40 min
Execution History? How long detailed logs and data snapshots from past runs are stored and accessible. Longer retention is needed for auditing, compliance, or debugging intermittent failures.	30 days
Data Transfer? Total data volume flowing through your scenarios per month. Most standard automations use kilobytes per run; file uploads, PDF processing, or bulk data exports consume more.	500 MB