In a recent training webinar, FormAssembly’s product experts walked through how repeatable sections work with the Salesforce Workflow Connector and how you can use them to reliably create, relate, and update multiple Salesforce records from a single submission, as well as other beneficial use cases.
Read on for a recap of the core use cases, configuration tips, and common pitfalls covered in the session, or watch the full webinar on-demand here.
Why repeatables matter in Salesforce workflows
Repeatables allow respondents to submit the same type of information multiple times in a single form without you having to predefine how many entries they’ll need. That flexibility is especially important when sending data to Salesforce, where one submission may need to create or update multiple related records.
Common scenarios include:
- Registering multiple people for a single event
- Uploading several supporting documents
- Capturing repeating details like allergies, dependents, or locations
FormAssembly’s Salesforce Workflow Connector was designed to handle these scenarios more cleanly and predictably than legacy connectors or logic added in at the form level only.
Key rule: always use repeatable sections (not fields)
Before we dive in, we want to set the stage with one of the most important takeaways from the webinar: Repeatables must be implemented as repeatable sections, not as individual repeatable fields, when used with the Salesforce Workflow Connector.
Even if you’re repeating a single field (like a file upload), it still needs to live inside a repeatable section for the connector to process each instance correctly.
With this in mind, let’s take a closer look at how it’s all done.
Creating multiple Salesforce records from one submission
The first demo showed how to create multiple Salesforce records – one per repeatable entry – using a single workflow action.
Example use case: An event registration form where a business can register up to 10 attendees at once.
How it works:
- Attendee details are collected inside a repeatable section.
- A Salesforce “Create Record” action is configured once.
- The action’s “Repeated Content” setting is mapped to the repeatable section.
- The connector creates one Salesforce record per repeated instance.
This approach ensures each registrant becomes a distinct Salesforce record without duplicating workflows or actions.
Relating repeatable records to the correct parent record
To associate child records (like registrants) with a parent record (like an event), each child record must receive the parent’s Salesforce ID.
The webinar covered two ways to do this:
1. Use a static parent record:
- Store the parent record ID (e.g., Event ID) as a hidden default value in the form.
- Map that value directly to the related field in Salesforce.
2. Use a dynamic parent record selection:
- Let respondents choose an event from a dropdown.
- Use a “Lookup Record” action to find the correct Salesforce record.
- Store the resulting ID in a workflow variable.
- Reference that variable in the repeatable record creation action.
Dependencies ensure records are only created when the parent record is successfully found.
Sending multiple file uploads to Salesforce
Repeatables are also ideal for handling multiple file uploads.
Example use case: An application form where applicants upload several supporting documents.
Best practice setup:
- Place the file upload field inside a repeatable section.
- Use a Salesforce “Upload File” action mapped to that section.
- Associate files to the correct Salesforce record using a workflow variable (such as Contact ID).
Preconditions can be added to prevent empty uploads from creating blank records.
Using formulas, variables, and preconditions together
One major advantage of the Salesforce Workflow Connector is its support for formulas and workflow variables, especially with repeatables.
Examples of this include:
- Linking first and last names per repeatable instance
- Customizing file names before sending them to Salesforce
- Reusing the same variable across “Update” and “Create” actions
- Skipping actions when required data is missing
These tools give you precise control over how and when each repeatable action runs.
Final tips for working with repeatables
To avoid common issues, we recommend:
- Using one repeatable section per Salesforce action
- Double-checking the “Repeated Content” setting if record counts look off
- Mapping parent IDs carefully to maintain correct relationships
- Adding preconditions to prevent blank or unintended records
- Testing workflows with multiple repeatable entries before going live
Repeatables are powerful, but only when configured intentionally. This webinar provided an easy-to-grasp overview of how they work, when they’re applicable, and “watch outs” to look out for when you implement them.
Want to explore further?
If you want to see the Salesforce Workflow Connector in action, you can book a personalized demo or start a free trial of FormAssembly today.
