AMPLUS Forms

Welcome to Sync, a no-code automation engine built directly into Amplus Forms.

It allows you to chain workflows that move and transform data across Amplus Forms and your external systems. Instead of relying on individual connectors and multiple tools to manage integrations and logic.

With Sync, you can:

• Trigger workflows based on events in Amplus Forms
• Move or transform data between systems
• Connect with external APIs and services
• Automate complex operational processes

In short, Sync becomes the glue that connects your operational data with the rest of your technology stack.

 Key Concepts: The Building Blocks 

To understand how Sync works, you only need to know three terms: Triggers, Actions, and Data Flow.

The Trigger 

Every Sync must start with a Trigger. This is the “event” that kicks off the process.

• Example: A user submits a form, or a Webhook is received from an external app.

Actions 

Actions are the individual steps that happen after the Trigger. You can stack as many Actions as you need in a single Sync.

• Data Processing: Generating a PDF from a template or mapping data fields.
• Services: Pushing data to a database or uploading a file to cloud storage.

Data Flow (Push/Pull & Upload/Download) 

To keep your workflows organized, we use specific language for how data moves:

• Push/Pull: Used for data, rows, and entities (e.g., Pull a customer record from Salesforce).
• Upload/Download: Used specifically for files (e.g., Upload a signed contract to Box).

 From “Connectors” to “Sync” 

In the past, a Connector did everything in one “black box.” In the new Sync engine, we’ve deconstructed those Connectors and more into smaller, reusable Actions.

Why the change? Flexibility. Instead of just sending a form entry to one place, you can now transform the data, generate a custom document, and send it to three different places at once.

 How a Sync Execution Works 

Every Action starts with a set of data fields received from the previous Action’s output.

For example, when a Form Entry Received trigger runs, it emits data in a FormEntryRichformat. The next Action in your chain (like “Generate PDF”) catches that data, uses it, and then passes its own output (the PDF file) to the next Action (like “Upload to Dropbox”).

 Quick Tips for Building Syncs 

• Start Small: Don’t try to build a 20-action Sync right away. Begin by replicating your existing Connectors as Syncs. Build a simple 3-action chain (Trigger > Transform > Send Email) and test it. Once that works, add more complexity.
• Outputs become Inputs: Every Action generates an “Output” packet. The subsequent Action can use those outputs as its “Inputs.” For example, the Generate Document output (the PDF file) is used as the input for an Upload to Cloud Storage action.