Drips

ActiveProspect partners with Drips to offer the actions of the Drips API directly through LeadConduit.

Drips can be found in the list of Recipients & Integrations:

Once added to the flow, you must choose one of following options:

• Insert New Lead: This allows you to send a single lead into the Drips system
• Close Lead: This is how you tell the Drips system to stop calling a phone number
• Converted Lead: This is how you tell the Drips system a lead converted on your end
• Add to DNC: Use this request to tell us when a lead has either opted out or has been disqualified

The UI will guide you through the rest of the setup steps. Data required for each step is described in detail below.

Insert New Lead

Required Configuration

• Drips Source Token

Required Lead Fields

• Phone: User’s Phone number / LeadConduit phone_1

Optional Mapped Data

• FirstName: LeadConduit first_name
• LastName: LeadConduit last_name
• State: LeadConduit state
• Postal: LeadConduit postal_code
• Country Code: The default is US (1)
• Company: LeadConduit company.name
• Email: LeadConduit email
• Sub1: LeadConduit campaign_sub_id_1
• Sub2: LeadConduit campaign_sub_id_2
• Sub3: LeadConduit campaign_sub_id_3
• DID: This allows you to override the DID we transfer a user to on a lead level. Do not use this field unless specifically instructed to do so.
• ExtHookUrl: LeadConduit webhook_url - If you would like to know the full results of this insert, submit a URL endpoint here. You must store the Drips original response token, as they will reference it in the webhook.

Close Lead

Required Configuration

• Drips Project Token

Required Lead Fields

• Phone: User’s Phone number / LeadConduit phone_1

Convert Lead

Required Configuration

• Drips Project Token

Required Lead Fields

• Phone: User’s Phone number / LeadConduit phone_1

Add to DNC

Required Configuration

• Drips DNC Token

Required Lead Fields

• Phone: User’s Phone number / LeadConduit phone_1

• screencapture-next-leadconduit-flows-5a8c96876995946a61835f2f-edit-steps-2018-05-02-17_36_16_1_.png50 KB