Skip to main content

Pick the simplest path that fits your workflow

Customers usually ask the same question in different ways: do we need a native integration, can we use a webhook, or should we start with a CSV? The right answer depends on how mature the workflow is and how much control your team needs.

How to choose

Choose this when the destination already exists in Leadpipe and your team wants the shortest path to operational use.
Choose this when your team needs logic, branching, or delivery into an internal system or unsupported tool.
Choose this when you are still proving value, validating fit, or testing a workflow before investing in automation.

Check whether your destination is supported

Open Integrations, search for the app, and inspect its connection requirements. If it is listed, follow Set up integrations. If it is absent, evaluate an HTTPS webhook receiver, your own API client, or a CSV import supported by the destination. A webhook can feed an automation platform that accepts incoming webhooks. That does not establish a native Leadpipe connector for every platform. Confirm the receiver, field mapping, and destination requirements before committing to the workflow.

Verify the data contract

Before enabling live automation, compare a test or exported record with the destination’s required fields. Confirm:
  • Which email is used as the contact identifier.
  • Whether repeat data updates a contact or creates another record.
  • Which activity fields arrive and whether you need separate API session reads.
  • Whether the selected segment, pixel, and send frequency match the intended audience.
Identification API responses and webhook events have different envelopes. Orbit results belong to a completed run and have their own schema. Do not reuse a parser without checking the corresponding reference or test payload.

A practical rollout order

  1. Start with the destination your team already uses every day.
  2. Push a narrow slice of high-signal traffic first.
  3. Confirm the records are useful in that destination.
  4. Add more destinations only after the first workflow is stable.

Common patterns

  • CRM first for sales teams
  • Slack first for visibility and fast internal testing
  • CSV first for a trial or lightweight review process
  • Webhook first for a custom ops workflow

Next steps