Workflow examples
Ten worked examples covering the connector families and node types DataLug ships today. Each example is one page with the same shape: a one-paragraph business problem, an at-a-glance summary, a canvas mockup of the node graph, a node-by-node configuration table, and a short list of common variations.
Start here: Meet Helix Beverages is the fictitious organization the rest of this section is set inside. It defines the partners, divisions, and pain points each example below maps to.
The catalogue
| # | Title | Connectors | Notable nodes | Direction |
|---|---|---|---|---|
| 1 | Salesforce -> Snowflake nightly sync | Salesforce, Snowflake | Transform | One-way |
| 2 | Salesforce <-> MSSQL contact sync | Salesforce, MSSQL | DbScript, Transform | Two-way (pipeline) |
| 3 | MySQL -> S3 CSV export with filter | MySQL, AWS S3 | Filter, Reshape | One-way |
| 4 | SFTP CSV -> PostgreSQL with compute | SFTP, PostgreSQL | Compute, Transform | One-way |
| 5 | Oracle ETL with DbScript prelude and cache | Oracle | DbScript, Cache | One-way |
| 6 | Google Drive -> SharePoint file copy with fork | Google Drive, SharePoint | Fork | One-way |
| 7 | PostgreSQL -> multiple targets with branch | PostgreSQL, Snowflake, S3, SMTP | Branch, Notification | One-way fan-out |
| 8 | Salesforce -> email digest with router | Salesforce, SMTP | Filter, Router, Reshape, Notification | One-way |
| 9 | Snowflake -> Google Sheets executive report | Snowflake, Google Sheets | Reshape, Transform | One-way |
| 10 | MSSQL <-> Salesforce reconciliation | MSSQL, Salesforce | DbScript, Cache, Transform | Two-way |
How to read these examples
Every example uses the same five sections:
- Why this example -- the business problem in one paragraph. If the problem doesn't match yours, skim to the next example.
- At a glance -- a bullet list of connectors and nodes used so you can spot the closest fit fast.
- Canvas -- an ASCII diagram showing the node graph. Use it to model your own canvas, then run the new-node wizard for each one.
- Step-by-step -- a table listing each node's action, key configuration fields, and the shape of data that flows through.
- Variations -- a short list of common tweaks you might apply (different DB family, schedule change, error-handling).
For per-connector setup details, see the Connectors sidebar. For per-node deep dives, see Nodes.