Form Integrations Setup

By default your form submissions get saved on the Run back-end (click the Form Submissions tab at the top of the CMS) but you may want to send your form data to other places as well. Run allows you to send form submissions to one or more destinations / integrations at a time, and different forms can have different sets of enabled integrations.

Note that we consider email an "integration", so you'll also follow this same process to get an email every time someone submits a form.

Click Create New Destination on the Form Builder in order to a new integration. Any integrations you add need to be enabled via the checkbox to their left (per each individual form) in order to actually function.

Each integration requires slightly different information to get set up, and we have help pages for each of them up here.

You can see whether a submission to a destination succeeded or failed on the Form Submission page (link at top of CMS). If it failed, you can hover your mouse on the word "Failed" to see the error message returned.

Submissions that did not go through to an integration because they were not enabled or because of a failure, can be resubmitted to a destination via the resubmit icon to the right of the word "Failure". If you have a lot of submissions that fall into this category, exporting as a CSV and importing directly at your destination may be easier than resubmitting one by one. The most common cause of submission failure is that the email provided is already in the integration database – this commonly causes failure during testing.

If the integration has features to sort people into different buckets, like tags, source codes, and lists ("segments"), we have two different methods to add that to form submissions.

In the integrations sections at the top of the form builder, you can select segments, and when selected there, they'll get attached to any submission of that form.

You can also attached segments conditionally based on whether certain checkboxes or radio buttons are clicked. To the right of the checkbox or radio button field in the form builder, you'll be able to select segments in the dropdown, in the same dropdown that allows mapping to custom fields.

With Run, you never need to worry about names, addresses, and phone numbers going through to the correct places on the destination. We have all of that mapped correctly out of the box. However, Run allows you to manually connect your forms to custom fields on the destinations as well.

First you'll create a custom field on the Run form builder, like Text for example. To it's right you'll now see a dropdown containing any custom fields from your enabled destinations that are possible to map to. Select whichever you like. (You'll need to create the custom fields at the destination first before they'll show up here.)

Run can only pull certain custom fields from your destinations. In most cases, that will include text, number, date, time, and booleans (booleans are true/false fields like checkboxes).

Run does not pull or sync multi-selection fields like dropdowns or radio buttons from your destination. However, you can set up multi-select fields on the Run side and connect them to simple text fields on the destination side. So, for example, you could create a custom text field on the destination called color. Then on the Run form builder, you could create a dropdown with red, yellow, and blue. When the form is submitted, the answer will go into the simple text field on the destination.

The Phone/Email opt-in field provided by Run will usually automatically connect to the corresponding field on the destination side, if one exists in their system by default. That's a field that denotes permission to contact and/or subscription status of the person.

You can also use the Disclaimer field, which is a custom field that can be connected by you to a field on the destination side manually.