Types of fields mapping supported during Integration
Sending data from Outgrow to your CRM is pretty simple using our Native and Zapier Integration. But sometimes you might want to send information from a field in Outgrow to your CRM, but there might not be a suitable field in your CRM to store the value coming in from Outgrow. In this case, you can create a Custom field in your respective CRM tool to accommodate this value coming in from Outgrow.
Types of fields available for mapping
Once integration is configured, all the data from Outgrow goes to your CRM tool in a String / Text format. Depending on the CRM tool that you use, it might accept that even when the field type in the CRM is number only, like in case of SalesForce. But some CRM's might reject them, so in general, we suggest users make Custom fields as text inputs.
Here is some more information about the different field type mappings that are supported by Outgrow:
A. String / Text field in Outgrow can be mapped with a custom field in your tool with Numeric Value as the field type.
B. String / Text field in Outgrow can be mapped with a custom field in your tool with String Value as the field type.
C. String / Text field in Outgrow can be mapped with a Dropdown type custom field in your tool.
D. String / Text field in Outgrow can be mapped with an Email type custom field in your tool.
E. Boolean field type in your CRM will only accept True or False values from Outgrow.
F. Original source in HubSpot only accepts a few specific values like Offline etc from Outgrow.
Important things to keep in mind
A lot of times, while mapping fields you will notice that the corresponding field in Outgrow from which the information is being sent will exist in your respective tool. But in some cases, it can happen that the corresponding field might not already be present. In such cases a new Custom field will have to be created. Two important things to keep in mind here are:
1. In case the Custom field in your respective tool is a Dropdown field, it will only accept data coming in String / Text format from Outgrow, if the preexisting field in Outgrow is also a Dropdown field.
2. In case the Custom field in your respective tool is a Numeric field with value as a numeric type, it will only accept data coming in String / Text format from Outgrow if the value of a preexisting field in Outgrow is also numeric.
3. If you have double opt-in turned on in Outgrow or in your own CRM tool then not all Outgrow submissions will be added to your email list. Leads will have to confirm via email that they completed the form to get added to a list.
Feel free to reach out to us at [email protected] in case you have any questions, and we will be more than happy to assist you further.
Updated about 4 years ago