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.| Option | Best when | Tradeoff |
|---|---|---|
| Native integration | You want the fastest path into a common downstream tool | Less flexible than building your own flow |
| Webhook | You need a custom workflow or a tool without a direct integration | Requires a more technical setup |
| CSV or manual export | You are validating value or handling lower volume | More manual and less real-time |
How to choose
Use a native integration
Use a native integration
Choose this when the destination already exists in Leadpipe and your team wants the shortest path to operational use.
Use a webhook
Use a webhook
Choose this when your team needs logic, branching, or delivery into an internal system or unsupported tool.
Use CSV first
Use CSV first
Choose this when you are still proving value, validating fit, or testing a workflow before investing in automation.
A practical rollout order
- Start with the destination your team already uses every day.
- Push a narrow slice of high-signal traffic first.
- Confirm the records are useful in that destination.
- 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
- Read Set up integrations for destination-level setup guidance.
- Read Set up webhooks if you need a more flexible delivery path.