Workflows

Workflows are the core of automation in Syncaut. They define how tasks are triggered, processed, and executed across your connected systems.

What is a Workflow?

A workflow is an automated process that runs tasks based on a trigger.

It connects different services and actions together using nodes. Once activated, a workflow runs automatically whenever its trigger condition is met.

Workflows can be used to automate operations such as order processing, data syncing, notifications, reporting, and more.

Creating a Workflow from Scratch

To create a new workflow:

1. Go to the Workflows section

2. Click New Workflow

3. That would take to your editor

4. You can give your workflow a name by clicking on the header on the workflow editor

   

5. Like here click on chubby-limited-insect and you would see an input.

You can now begin adding nodes and building your automation.

The Workflow Canvas (Nodes + Connections)

The workflow canvas is where you design your automation.

A workflow is made up of:

• Nodes — individual steps (triggers, actions, logic)

• Connections — links between nodes that define the flow of data

You build a workflow by:

1. Adding nodes to the canvas

2. Connecting them in sequence

3. Defining what each node does with the node dialog which you can open by double clicking on a node or using the settings icon you see when you click once.

   

Data flows from one node to another based on how they are connected.

Workflow Triggers

Every workflow starts with a trigger. A trigger defines when the workflow should run.

Syncaut supports multiple trigger types depending on your use case.

Manual Trigger

A manual trigger allows you to run a workflow on demand.

This is useful for:

• Testing workflows

• Running one-time operations

• Debugging automation

Scheduled Trigger (Daily / Weekly)

A scheduled trigger runs workflows automatically at a defined time.

You can configure:

• Daily schedules

• Weekly schedules

• Specific times

This is useful for recurring tasks such as reports, syncs, or batch processing.

HTTP Request Trigger (Webhook)

The HTTP Request trigger allows external systems to trigger your workflow using a webhook.

When a request is sent to the provided endpoint, the workflow starts instantly.

This is useful for:

• Receiving real-time events from external services

• Integrating with systems that support webhooks

• Triggering workflows from custom applications

You can send data in the request, which becomes available inside your workflow for processing.

Google Form Trigger

This trigger runs when a new response is submitted to a Google Form.

Useful for:

• Capturing leads or submissions

• Automating form-based workflows

• Triggering follow-up actions

Stripe Trigger

This trigger runs based on events from Stripe.

Examples include:

• Successful payments

• Subscription updates

• Failed transactions

This allows you to automate billing-related workflows and financial operations.

Running & Testing a Workflow

Before activating a workflow, it’s important to test it.

To test a workflow:

1. Use a manual trigger or test mode

2. Run the workflow

3. Check each node’s output

4. Verify that data flows correctly

Testing helps ensure your workflow behaves as expected before going live.

Viewing Execution History

Syncaut keeps a record of workflow executions.

You can view:

• Past runs of a workflow

• Status of each execution (success or failure)

• Data passed between nodes

• Errors and logs

Execution history helps you:

• Debug issues

• Monitor performance

• Ensure your automation is running correctly