What Types of Automated Lead Entry Does Shape Support?
Shape Software supports CSV file imports, POST URL, Zapier Webhooks, and pre-built or custom-built API Integrations. Post URL, Zapier Webhooks, and imports are preferred as the functionality is already in place without any development timeframes or related costs.
Import lists can be a Comma Delimited Text (.csv) file. Note that other applications can export records in these formats. No more than 3,000 contacts can be uploaded at one time on default systems. To increase your import limits, communicate your needs upon system discovery, we have the data store option that supports mass importing & lookups. After uploading your list, you will be able to match the field names for your data. For field name definitions, you can review the Import Field Guide within your import settings page in your system. Follow these steps before you start importing any data. Use your existing software or application to create an export file. Clean up the import file for accuracy and consistency. This involves updating the data to remove duplicates, delete unnecessary information, correct spelling and other errors, and enforce naming conventions. Compare your data fields with the Shape Software fields you can import into to verify that your data will be mapped into the appropriate Shape fields. You might need to fine-tune the mapping before starting the import. For details, see Import Field Guide within your import settings page for help.
Please note that Zapier Webhooks are available without the need for a dedicated API integration. Need a specific integration? Let us know what you would like to integrate Shape with. We will be requesting API docs as well as your expectations for the integration. After reviewing the docs alongside the expectations, we will follow up and let you know the details on what we will be able to accomplish based on what is available within the API documentation and discuss any possible changes or restrictions. We will also provide an estimated timeline for completion.
Generic Posting URL Instructions for Shape Software
These are instructions for submitting records into Shape Software using the default integration.
Posting URL Format
Shape’s posting URLs have a consistent format. There are two parts of the URL that vary:
CRM ID — The 4 character flow ID that uniquely identifies your system.
Source ID — The 24 character source ID generated by Shape that identifies the source of the lead.
NOTE: The CRM and Source IDs are very important to ensure the lead goes into the correct system and is attributed to the correct source. The sample URL above will not work because it contains placeholders for CRM ID and source ID.
Setting Up Posting URLs via “Marketing Sources”
The actual URL must be created in the Shape “Marketing Sources” settings page. Create a new source if one does not exist or edit or open an existing one. A unique posting URL is created for each source within your system.
Shape only supports receiving leads using a request because POST is more secure than GET.
Each system contains a unique set of acceptable fields. View and/or export these fields via the “Marketing Sources” settings page. Although the individual posting URL is unique to each source, the field mappings will be the same for every source.
About Data Types
The supported fields table lists each field supported by Shape. Each field has an associated type, which is used to help make sense out of the data you provide. If a field is provided with a value that cannot be interpreted as the expected type, no error will be given. Nevertheless, your leads have the best chance of making it through the system when the data provided in each field is comprehensible to Shape.
When a lead is submitted, Shape provides real-time feedback in the HTTP response body. This feedback identifies which one of three possible outcomes occurred. The outcome is derived from a series of actions and rule evaluations that take place while the lead is processed through the system.
The possible outcomes are:
Any failure or error can be reported to email@example.com. Please be sure to include the full HTTP request information (POST, URL, and parameters being sent).