Destinations

Destinations are reusable configurations that define where and how lead data is sent to external systems after processing in a flow. They represent the final delivery point for qualified leads, whether that's a CRM, marketing automation platform, partner system, or any other business application.

Destination

An internal representation of a Prismatic instance.

name
string

A customizable name of the destination.

integration_name
string

The name of the integration as published in the Marketplace.

integration_icon_url
string

Pre-signed URL for the integration icon.

instance_id
string

The Prismatic instance ID.

Array of objects

A list of actions available in the configured instance. These map to Prismatic "flows" within an instance.

object

Contains data on flows in which the destination is used. This field is optional and is only included when the include=flow_usages query parameter is included in the request.

{
  • "name": "Salesforce",
  • "integration_name": "string",
  • "integration_icon_url": "string",
  • "instance_id": "string",
  • "actions": [
    • {
      • "name": "Add Lead",
      • "action_id": "Add Lead",
      • "webhook_url": "string"
      }
    ],
  • "flow_usages": {
    • "count": 0,
    • "flows": [
      • {
        • "id": "5fd4371e940df5a34a3888b2",
        • "name": "string"
        }
      ]
    }
}

Key Concepts

What Are Destinations?

Destinations are pre-configured connections to external systems that receive lead data. Unlike recipient steps that are configured individually within each flow, destinations are configured once at the account level and can then be reused across multiple flows. This "configure once, use many times" approach ensures consistency and reduces setup time.

Powered by Prismatic

Destinations are powered by Prismatic, an embedded integration platform that provides:

  • A marketplace of pre-built integrations for popular business systems
  • Secure credential management
  • Field mapping capabilities
  • Multiple actions per destination (e.g., "Create Lead", "Update Contact", "Add to Campaign")

Configuration Process

Destinations must be configured through the LeadConduit application interface because the setup process requires:

  1. Integration Selection: Browse and select from a marketplace of pre-built integrations (Salesforce, HubSpot, Marketo, custom webhooks, etc.)

  2. Authentication Setup: Securely configure credentials for the external system, which may involve:

    • OAuth authorization flows
    • API key management
    • Username/password authentication
    • Custom authentication headers

  3. Instance Configuration: Define specific settings for your instance of the integration:

    • Which Salesforce organization to connect to
    • Which HubSpot account to use
    • Which mailing lists or campaigns to target
    • Custom endpoint URLs for webhooks

  4. Field Mapping: Interactively map LeadConduit fields to destination fields:

    • Match lead fields to CRM fields
    • Set default values
    • Configure data transformations
    • Handle custom fields

  5. Testing & Validation: Verify the connection works properly before using in production flows

Using Destinations in Flows

Once configured, destinations can be:

  • Queried via the API to see all available destinations
  • Added to flows programmatically via the API
  • Reused across multiple flows without reconfiguration
  • Updated centrally with changes reflected in all flows using them

Delivery Rules

  • Lead data is only sent to a destination if all prior flow steps complete successfully
  • Any error in preceding steps will prevent delivery to protect data quality
  • Each destination can support multiple actions, allowing different operations on the same system

Multiple Actions

A single destination can offer multiple actions. For example, a Salesforce destination might provide:

  • "Create New Lead" - Adds a new lead record
  • "Update Existing Contact" - Updates contact information
  • "Add to Campaign" - Enrolls the lead in a marketing campaign
  • "Create Opportunity" - Converts qualified leads to opportunities

API Capabilities

While destinations cannot be created or modified via the API, you can:

  • List all configured destinations for your account
  • View destination details including available actions
  • See which flows use each destination (with include=flow_usages parameter)
  • Add existing destinations to flows
  • Remove destinations from flows

List all destinations configured for the account

The /destinations resource is used to query destinations which have been configured in the LeadConduit app. If no destinations are configured for your account, this resource will return an empty array. Destinations returned from this endpoint can be added to flows.

SecurityAPIKey
Request
query Parameters
include
string

Additional properties to include in the response.

Value: "flow_usages"
Responses
200

OK

401

Authorization information is missing or invalid.

get/destinations
Request samples 
Response samples 
application/json
[
  • {
    • "name": "Salesforce",
    • "integration_name": "string",
    • "integration_icon_url": "string",
    • "instance_id": "string",
    • "actions": [
      • {
        • "name": "Add Lead",
        • "action_id": "Add Lead",
        • "webhook_url": "string"
        }
      ],
    • "flow_usages": {
      • "count": 0,
      • "flows": [
        • {
          • "id": "5fd4371e940df5a34a3888b2",
          • "name": "string"
          }
        ]
      }
    }
]