Using Appended values learned from a prior LeadConduit step

Example: Sending a value from an add-on step to your CRM

Sometimes you’ll want to record the values that are appended by an add-on step, and then include them in the delivery to a second system, such as your CRM. Here’s how.

How do you add values appended by an Add-On to your CRM delivery?

• Log into account.activeprospect.com and pick LeadConduit.
• Click on your flow from the dashboard or from Flows
• Edit the flow and verify the add-on step has been added to the flow in a position before your final delivery step
• Click on your CRM delivery step and click “Edit Field Mappings”
• Click the “+” at the end of an existing mapping to add a new line
• Search for the name of the add-on you’re using in your flow on the left, and pick an appended value from the list; and on the right, type the name of the property where your CRM expects to receive this appended value.
  In this example shown below, we’ll search for Anura, which was previously added to this flow, selecting a value on the left that tells us the information we want to know–e.g., Anura’s “Is suspect” value–and on the right, typing in the “ip_warning” field that our CRM expects to be received.

• Click “OK” and save the flow at top right, and wait to see the value is sent with the next lead.

Example: Querying an external system for an authorization token (oauth2)

Many systems employ oauth2 or other methods to provide a limited-use authorization “Bearer” token to reuse subsequently for authenticating a lead delivery request.

For example, often we see a grant request including parameters such as these, which replies with a Bearer token we can use in a subsequent delivery:

grant_type=client_credentials
client_id=3MVG9Xjf0O2Peyd5ctUTbT2gQuODXzWCZXtF0g10zVMZ5a5RhYVLPb15qnws
client_secret=AC617C29CCC06CB796536FBDE622E6FC3EF0B7EDA
scope=myinstance.example.com

Put together the delivery to the auth endpoint in LeadConduit via a json custom delivery or urlencoded custom delivery.) This auth request step will almost always reply with a json formatted response, so appended values from the response will automatically be added in your flow.

Validate that you’ve received a token

• Drill into a test lead in Leads->Lead events
• Click on the auth endpoint step you’ve built, called “auth token request” on the left in the example below so that it is highlighted in blue, and expand Technical Details in the right pane. Scroll down, if needed, and examine the Response for a value giving the token.

Edit your final endpoint delivery to use this access token in an Authorization header

• Edit the flow and edit/create your final delivery step
• Click on your final delivery step and click Edit Field Mappings
• Add a line to the field mappings by clicking the “+” at the end of an existing mapping
• On the left, type “Bearer” followed by the a space. Then type the name of the delivery that is generating the token, auth token request in this example, picking the appended token value as in the sample below; and on the right, pick “Header” and type in “Authorization”, which will create an Authorization header to hold this value.

• Click “OK” at the bottom of your mappings and then “Save” at top right to save the flow.

Example: Querying an external system to check for duplicates

Sometimes, you may want to query an external system that offers an API to learn whether a phone or email is a duplicate with one that is already known and previously contacted. Here are the steps, once you have the details for the external system’s API:

• Edit the flow and edit/create an integration to the external system, such as the “precheck” Custom step below, which reaches out to an API that returns a json value “duplicate,” set to “true” or “false” (for example).
• Follow the integration step by a filter step checking for the value appended to the flow by the new step, in order to stop processing the lead if a value appended by your integration is not the desired outcome. This filter below checks whether the value “duplicate” returned by the precheck is “true” or “false”

• Click “Save” at top right to save the flow

This strategy also can be used for customized solutions with integrations that check any value in a lead with the help of an API available resource, such as an API that checks zip codes or other data.

• Screenshot_2023-06-04_at_5.55.47_PM.png100 KB
• Screenshot_2023-06-04_at_7.50.15_PM.png200 KB