Supabind

Export & Sync

Send a transformed file where it needs to go-into Odoo or Akeneo, a MySQL or PostgreSQL database, a Google Drive folder, or an FTP/SFTP server-as the final step of a workflow.

Quick Navigation

• Odoo Sync• Akeneo Sync• Database Export• Google Drive Export• FTP/SFTP Export• Chain Multiple Destinations

Overview

Export & Sync nodes are the last stop in most workflows. Each one takes whatever file reaches it-usually the output of a Transform Template node-and delivers it to a specific destination using a saved connection. You can attach more than one Export & Sync node to the same upstream node if a single transformed file needs to go to multiple places.

Odoo Sync

Push the transformed file's rows into Odoo using a saved sync template.

Odoo Sync

Sync data to Odoo using a saved template

Steps

  1. Add the Odoo Sync node and connect it to the node feeding it a file.
  2. Open the node and select a saved Odoo sync template, which defines the model and field mapping to use.
  3. Run the workflow to push matching rows into Odoo; check Execution History for created, updated, or skipped record counts.

Akeneo Sync

Sync product data into Akeneo PIM using a saved sync template, the same way Odoo Sync works for Odoo.

Steps

  1. Add the Akeneo Sync node and connect it upstream to a transformed file.
  2. Select the saved Akeneo template that maps your columns to the right attributes and family.
  3. Run the workflow and confirm the sync in Akeneo or in Execution History.

Both Odoo Sync and Akeneo Sync rely on templates created outside the workflow builder-set those up first if you haven't already.

Database Export

Write the transformed file into a MySQL or PostgreSQL table.

Steps

  1. Add the Database Export node and connect it to the transformed file.
  2. Choose the database connection, target table, and whether to insert, upsert, or replace rows.
  3. Run the workflow and verify row counts in Execution History.

Google Drive Export

Drop the transformed file into a Google Drive folder-useful when a downstream tool or teammate expects the file to just appear there.

Steps

  1. Add the Google Drive Export node and connect it upstream.
  2. Connect your Google account if you haven't already, then choose the destination folder.
  3. Set a file name pattern if you want each run to avoid overwriting the previous export.

FTP/SFTP Export

Push the transformed file to a remote FTP or SFTP server-the export counterpart to FTP/SFTP Import.

Steps

  1. Add the FTP/SFTP Export node and connect it to the transformed file.
  2. Enter the server host, port, credentials, and the destination path.
  3. Run the workflow to confirm the file lands where expected.

Server credentials are stored per-node, so you can export to a different server than the one a workflow imported from.

Chain Multiple Destinations

A single transformed file can fan out to more than one Export & Sync node in the same run.

Steps

  1. Connect two or more Export & Sync nodes to the same upstream node's output.
  2. Configure each node independently-for example, Odoo Sync and Google Drive Export can run from the same Transform Template output.
  3. Use Run Now to confirm both destinations succeed before activating the workflow.

If one destination fails, check Execution History-other branches from the same node still complete independently.

Was this article helpful?

Need More Help?

If a sync or export isn't landing where you expect, or a destination node keeps failing, our support team is here to help.

Contact Support