Syncaut is built around a few core concepts that help you organize automation, manage integrations, and run operations across teams and clients.
Understanding these concepts will help you design workflows efficiently.
Workspaces organize your environment.
A workspace can represent a client, team, store group, or project. Each workspace keeps its workflows, integrations, and templates separated from others.
Users can operate with a single workspace or multiple workspaces within one account. This allows agencies to manage many clients while keeping operations isolated and secure.
Workspaces also allow you to invite collaborators so teams can build and manage automation together.
Workflows are automated processes that run tasks across your connected systems.
A workflow is created by connecting nodes that define how data moves and what actions should occur. Once activated, workflows automatically run whenever their trigger conditions are met.
Workflows can automate tasks such as syncing data between systems, processing store events, triggering fulfillment actions, or updating operational records.
Templates are reusable versions of workflows.
Any workflow can be saved as a template and reused across workspaces. This allows teams and agencies to standardize automation processes and quickly deploy them for new clients.
Templates can be:
Shared across multiple workspaces
Shared with team members
Published publicly for other users to discover
Kept private for internal use
Templates make it easy to replicate proven automation setups without rebuilding workflows from scratch.
Nodes are the building blocks of workflows.
Each node performs a specific function such as triggering a workflow, performing an action, or transforming data.
Examples of nodes include:
Triggers from external services
Actions that send or update data
Logic nodes that filter or route information
Data transformation nodes
By connecting nodes together, you define how information flows through your automation.
Syncaut follows a Bring Your Own Key (BYOK) model for integrations.
Instead of using shared platform credentials, users connect their own API keys and authentication credentials for services they want to automate. This ensures that workflows operate directly within the user's own accounts.
Credentials are stored securely and can be used by workflows to authenticate requests to external services such as payment systems, logistics providers, data platforms, or AI services.
Using BYOK provides several benefits:
Full control over your integrations
No shared platform access to third-party accounts
Greater security and transparency
Flexibility to connect any supported service using your own credentials
Credentials can be managed and reused within a workspace when building workflows.
Navigate