Using Spark as the Action App in Zapier

Agent

This field determines whether or not an agent tag is applied to the contact in Spark. Typically, this will be the answer to “Are you an Agent/Realtor.” 

Returning “yes” or “TRUE” will apply the agent tag to the contact and returning “no” or “FALSE” will not apply the agent tag to the contact.

This is a prime example of when paths are suitable - create one path for Agent=yes/true and a separate path for Agent=no/false to successfully denote agents and non-agents within Spark.

This field determines the rating registrants receive within Spark. These are unique to each project and can be found within the project’s API documentation.

If you are using paths to denote agents vs. non-agents, you may choose to apply one rating to agents and a different rating to non-agents.

This field applies a registrant’s answers to project questions to their profile within Spark. Enter the appropriate question ID (unique to each project and found in the API documentation) in the left field and the answers to the question, separated by commas, in the right field.

Note that you should enter the answers exactly as they are in the project questions (Menu → Forms → Project Questions). For example, if the answers given are 1 bed, 2 bed, 3 bed, do not enter them as 1 bedroom, 2 bedroom, 3 bedroom.

Add additional Q&A fields as appropriate.

If the project has created standardized contact fields and this information is collected on your form, it can be posted to each registrant’s profile within Spark using the appropriate Standardized Field ID. Standardized Field IDs are unique to each project and can be found in the API documentation. Enter the ID in the left field and match the right field to the appropriate data from your trigger app.

This field allows for tracking a contact’s registration source against specific forms, apps and integrations. These are unique to each project and can be found within the project’s API documentation.

An alternative to the Registration Source ID, this field assigns a registration source to the contact by entering the name associated with the source. These are unique to each project and can be found within the project’s API documentation.

Note that you should answer the name exactly as it appears in the API documentation. For example, if the name is “Corporate Website”, do not enter “Corp site.”

If your form doesn’t have a marketing source or “how did you hear about us” question, you can use this field to set a marketing source

For example, if the Zap is posting registrants from a Facebook form to Spark, you might choose to enter “Facebook Ad.”

Note that if the source already exists as an answer to the marketing source question, you should enter the source exactly as it is given, for example, “Facebook Ad” instead of “FB ad.”