File-based handoff
Report exports
Export the supported report rows for analysis or client review. Check the date range, fields, and account before using the file in another tool.
Explore CSV exportsKeep the context moving
Your call data has a next step.
A report for your client. An event for your workflow. A connection to your own software. Choose the approach that fits the information you need to move.
Three ways to connect
Start with the job, then choose the connection.
This directory covers the connection methods described in Lead Source's product: report exports, event delivery, and account API access. These methods serve different needs. A downloadable report is useful for a periodic review; an event message is useful when something changes; a custom connection can support your own software's specific workflow.
A method is not the same as a prebuilt connector for every CRM or advertising platform. Confirm the information available, the receiving tool's requirements, and the work needed before depending on a connection.
Event-based delivery
Webhooks
Send a message to a receiving system when a supported call or lead event happens. Review delivery results and handle failed attempts.
Explore event deliveryCustom development
Account API access
Use supported account data and operations in a custom connection. Implementation, permissions, and end-to-end testing are part of the work.
Explore API capabilitiesA connection with a purpose
Source → information → action.
-
Name the outcome
Describe what the next tool should do: prepare a client report, update a lead process, or support an internal review.
-
Choose the information
Identify the supported fields and events needed for that outcome. Send the minimum useful information.
-
Verify both sides
Check that Lead Source can provide the information and that the receiving tool can accept and interpret it.
-
Review the complete result
Test a successful handoff, a failure, and a repeated event. Assign someone to maintain the connection after it goes live.
Know the difference
A shared vocabulary for evaluating integrations.
- Prebuilt connection
- A supported connector with a defined setup and behavior. Do not assume one exists simply because both products provide an API.
- Custom connection
- Software built around supported interfaces. Someone needs to implement it, handle changes, and maintain it.
- Export
- A point-in-time file. Changes made later in either system do not automatically update the other copy.
- Event delivery
- A message about a supported change. The receiving tool must decide what to do with it and avoid repeating work when a delivery is retried.
Built for the workflow you can verify
Useful connections begin with clear boundaries.
Before sending call information to another service, review the people who can access it there and the purpose of the transfer. An export or connection can create another copy of information with its own retention period. Keep credentials private, document who owns the workflow, and revisit the arrangement when a tool is retired.
Detailed developer setup remains separate from this directory. These pages explain what each connection approach is for, so a business owner and the person implementing it can agree on the same outcome.
Frequently asked questions
A few more things, explained.
Explore the details. Open a question for the answer.
Which connection methods are covered in this directory?
The directory covers supported report exports, webhook event delivery, and account API access. Each method has a different purpose and does not imply a prebuilt connector to every third-party tool.
Does Lead Source list a native connector for every CRM?
No. A CRM name should only appear as a supported native integration after that connection has been implemented and verified. Contact the team about the exact tool and workflow you need.
When is a CSV export the right integration approach?
An export is useful for a periodic report, a spreadsheet review, or a controlled handoff. It is a point-in-time copy and does not automatically keep two systems up to date.
When should I consider an event-based connection?
Consider event delivery when another tool needs to react to a supported call or lead change. The receiving system needs a defined action and a way to handle retries.
When does a custom API connection make sense?
A custom connection can help when your own software needs supported account data or operations. It requires implementation, appropriate access, and tests for the complete workflow.
Can I connect a tool just because it also has an API?
Not automatically. The required information and actions must be supported on both sides, and someone must implement the mapping, access, error handling, and maintenance.
What information should I bring when asking about an integration?
Name the receiving tool, the outcome you want, the information involved, and how often it needs to move. Explain who will maintain the connection once it is running.
Does an integration inquiry require me to share an API key?
No. Describe your requirements without sending credentials. Keys are sensitive access information and should only be handled through an appropriate implementation process.
Can a receiving system process the same event more than once?
Repeated delivery is possible in a retrying workflow. The receiving system should recognize an event it has already handled and avoid creating duplicate records or actions.
Does successful event delivery prove the business action happened?
No. A receiver accepting a message is different from completing the intended action. Verify the final result in the destination tool as part of your testing.
Will editing an exported spreadsheet change Lead Source records?
No. A downloaded report is separate from the application's records. Editing that file does not write changes back into Lead Source.
How should agencies organize connections for several clients?
Define the correct account and access for each client, keep destinations clearly separated, and test that information arrives in the intended workspace before expanding the workflow.
What should I check before sending call data to another tool?
Confirm the purpose, required fields, receiving access, and retention expectations. Send only the information the workflow needs and review any additional copies it creates.
Does this integrations directory include developer setup instructions?
No. It explains the connection choices and their responsibilities. Detailed API reference and setup documentation remain separate from these marketing pages.
How can I request a connection that is not listed?
Use the Contact page to name the tool and describe the workflow. A request helps assess fit but does not promise a delivery date or confirm that the connector already exists.
Meet your next growth tool
Tell us what needs to happen after the call.
Start with the tool and the outcome. We’ll help you assess the connection requirements.