This tutorial moves data between a Connected App (Salesforce, HubSpot, NetSuite, …) and another system — typically a relational database, but the destination can be anything Etlworks supports. Connected App connectors work like database connectors, so the flow setup is almost identical.
How do I set this up?
- In Connections, create a connection for the Connected App. The connector lives under Connected Apps (Salesforce, HubSpot, NetSuite, and others). Test the connection.
- Create the destination connection — for example, a relational database or another SaaS app — and test it.
- In Flows, create a new Connected App to… flow.
You can also use a Database to… flow type. Connected App connectors function like database connectors, so the two flow types are interchangeable here.
- Add a transformation:
- FROM — the SaaS app or the database, depending on direction.
- TO — the destination connection and table or object.
- Optional: click Configure and enter a custom Source SQL. Leave it blank to extract everything from the source object.
- Optional: configure per-field mapping when source and destination schemas differ.
- Test the transformation.
- Optional: enable MERGE (UPSERT) to update existing records.
Note: Enable Predict Lookup Fields to let the flow pick keys automatically, or set them manually as fully qualified table=fields pairs in Lookup Fields:
- Optional: configure change replication using a high watermark to load only changed records.
- Optional: to fully refresh destination tables on every run, add this to Before SQL:
truncate table {TABLE} - Add as many source-to-destination transformations as you need.
- Save the flow and execute it manually.
- Schedule the flow: go to Schedules and create a schedule to run it periodically.
Next steps
To move many objects at once using a wildcard, see How to ETL data from tables matching a wildcard.