Salesforce Custom Object Data Destination


This feature is available on the following tiers: Enterprise, Advanced.



The Salesforce Custom Object Data Destination creates or updates records in Salesforce when mobile forms are submitted. The Custom Object destination can also be used with any Standard Object in Salesforce, including objects in Field Service Lightning.

Note: ProntoForms currently supports Salesforce API version 42 for this data destination. Salesforce does not currently support sending data from repeatable sections.

Image result for salesforce Organizations of all sizes use the Salesforce platform to manage customer relationships and power their business in the cloud. Looking for two-way integration?  Read more about the ways ProntoForms can connect to Salesforce. 

Set up the Data Destination

Create the data destination, selecting Salesforce Custom Object Data Destination as the type.

1.  Name/Forms

  • Name the destination.
  • Manually link existing forms to the destination.


2.  Filtering

  • Optionally set up filter rules.  The data destination will only create/update records when these conditions are met.


3.  Connection

  • Connect the destination to Salesforce.  Use an existing connection, or set up a new Salesforce Connection.


4. Custom Object Fields

Custom Object Information

Enter the API Name of the custom object. Read here for details on how to locate this in Salesforce.

Custom Fields

Send data to the object's standard or custom fields.  
Note: The Geolocation custom field is currently not supported.

    • Salesforce API Name:  Enter the API name of the standard or custom field
      (This can be found through the "Describe Salesforce Object" button in ProntoForms).  
    • Value Expression:  Use Data Record Expression Language (DREL) to reference data in form submissions using the question label.   



4. Attachments

Documents and images collected in ProntoForms can be sent to Salesforce and attached to records.

Attachment Upload Location

This option affects both Documents sent through destinations, as well as any image, audio, or file attachments.  It controls which location they are stored in once added to a record. 


Depending on your Salesforce configuration and version, attachments on records may be stored in "Files" or "Notes & Attachments".   Choose the option that matches your current Salesforce setup. 

Choose which image, audio, file, and signature attachments to send to Salesforce.

    1. Locate the attachment (photo, signature, audio, or file attachment) type question in the form builder and find the unique ID.


    2. Navigate to or create a Salesforce Custom Object data destination, and then select the Attachments tab.
    3. Enter the appropriate unique IDs into the Attachments to send field. Use commas to separate the unique IDs.


Note: These attachments are handled as defined on the Update Query tab, where you can choose to create new records or update existing records.


5.  Update Query

  • By default, new records will be created in Salesforce when the destination executes. 
  • Optionally set up the data destination to update existing records.
  • If you wish to write form data to existing custom objects, you must match a custom object field name with the corresponding field value in the form.
  • For example:
    This shows that the form submission data will always be written to an existing Salesforce Custom Object containing the "Customer Selection" value in the "Name" field in Salesforce.


Destination Response Outputs

Destination response outputs allow users to make sequential requests, typically to create parent-child relationships when creating records. For example, a user might want to create a record in a first destination, and have destination response outputs pass the ID for that record to the next destination to add an appropriate attachment to it.

Click here for more information: Destination Response Output


Testing and Troubleshooting Data Destinations

Test all data destinations before using them in production. This is key to ensuring that ProntoForms data is received. Please read the recommendations for testing and troubleshooting data destinations.

[ top ] 

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request