Workflow FAQ

A Transform Template is a specific set of data-cleaning steps (filters, joins, etc.). A Workflow is the 'orchestrator' that decides when to run those steps (Trigger), where to get the file (Source), and where to send the result (Sync).

By using a Schedule trigger or a Webhook trigger. A Schedule lets you run the workflow at specific times (daily, weekly), while a Webhook trigger waits for an external system to ping Supabind to start the run.

Currently, a standard workflow run processes one primary source file. However, you can use Utility nodes like 'HTTP Request' to pull in supplemental data during the run.

The status bar next to the workflow name will show 'Unsaved' if there are pending changes. Always click the purple 'Save' button in the top right to commit your node layout and configurations.

Use the 'If / Else' Utility node. This allows you to check a condition (e.g., if total_sales > 1000) and send the data down two different paths—for example, syncing high-value rows to Odoo and low-value rows to a Google Drive folder.

Delay nodes are useful when the destination system (like a PIM or ERP) has rate limits or needs a few seconds to process an earlier request before receiving the next one.

Yes. Use the 'Set Variable' node to store a value from a JSON output. You can then access it in downstream nodes using the {{ variables.name }} syntax.

Click 'Execution History' in the builder toolbar. This opens a log showing every time the workflow was triggered, including timestamps and whether the sync to your destination (like Odoo or Akeneo) was successful.

Deactivating a workflow pauses all Scheduled and Webhook triggers. The workflow will not run again until you click 'Activate.' This is useful for maintenance or when making major logic changes.

Yes, click 'Download JSON' in the toolbar to get a portable version of your workflow configuration. This can be useful for version control or sharing logic with the Supabind support team.

You can sync directly to production systems like Odoo ERP and Akeneo PIM, or export files to Google Drive, FTP/SFTP, or a SQL Database (MySQL/PostgreSQL).

You can cancel an active run from the 'Execution History' or the 'Transform Queue' tab in your main dashboard.