# How to answer integration questions on LinkedIn
> Answer integration questions on LinkedIn by confirming the connection fast, then tying it to the buyer's workflow. A practical guide for founders and B2B sellers.
- HTML: https://getkinlead.com/reply-to-prospect-asking-about-integrations
- Markdown: https://getkinlead.com/reply-to-prospect-asking-about-integrations.md

**Short answer:** When a prospect asks about integrations on LinkedIn, they're asking if your tool creates more work for them. Stop explaining how the API works and explain the business result the integration produces. Shift the focus from the connection to the outcome.

## Identify the fear behind the question

Most founders and SDRs treat integration questions as a checklist. If the prospect asks about Salesforce and you have it, you say yes. If you don't, you say no. That misses the point. A technical question usually stands in for a fear about their daily workload.

The prospect doesn't care about the plumbing. They care about what changes on Monday morning. Two fears show up most: the team won't use another tool, and the data will end up in two places with nobody owning the cleanup. A third fear sits underneath both: they will look bad for choosing you.

When someone asks 'does this work with HubSpot' on LinkedIn, they are often halfway through a buying decision and checking whether your product will create extra admin. Answer the admin question, not the API question. Ask what they do today before you describe what you do tomorrow.

**The technical answer**

- Does this integrate with Salesforce? -> Yes, we have a native Salesforce integration.
- Do you have a Slack integration? -> Yes, we use a webhook to push notifications to Slack.

**The outcome answer**

- Does this integrate with Salesforce? -> Yes. Your reps can see lead intent without leaving the CRM, so they don't copy and paste records between tabs.
- Do you have a Slack integration? -> Yes. Your team gets alerts in the channel they already watch, so leads don't sit idle until someone checks a dashboard.

## The pivot framework

To move a prospect from a technical hurdle to a discovery call, use a pivot. Acknowledge the tool they named, confirm the connection in one line, then describe the result for the person doing the work. Keep the API out of the first reply.

If you spend three paragraphs explaining endpoints, you've turned a sales conversation into a support ticket. The buyer can read docs later. Right now they want to know whether the integration removes a task they hate. A good answer makes the next question about their process, not your documentation.

1. **Acknowledge the tool.** Mention the specific software they named. This proves you read the message and aren't using a script.
2. **Confirm the connection.** Give a one sentence yes or no. If there's a workaround, state it plainly without over-explaining the mechanics.
3. **Describe the business outcome.** Explain exactly how this integration saves time, makes money, or reduces stress for the end user.
4. **Ask a workflow question.** End with a question about how they currently handle that process to shift the focus back to their pain.

## Ask one workflow question before you answer

Before you describe any connection, ask how the work gets done now. The answer tells you whether the integration matters or whether the buyer is still hashing out a shortlist. It also gives you the exact words to use in your reply.

Keep it to one question. 'How are you moving those leads into HubSpot today?' is enough. If they say 'we don't,' you have a different conversation. If they say 'our intern copies them every Friday,' you know the pain is real and the fix is easy to explain.

Use the answer in your next message. Repeat their tool and their process back to them, then confirm the connection. That sequence shows you listened, and it makes the outcome specific instead of generic. It also stops you from writing a feature list nobody asked for.

```
Which tool holds the record today?
Who updates it, and how often?
What happens when the record is wrong or late?
```

## Writing the response

The tone should be helpful and confident. You aren't asking for permission to be a vendor. You're showing them how their week gets easier. Avoid words that describe the software instead of the result. Say what the person stops doing.

Keep the reply short. Two or three sentences is enough for a LinkedIn message. If the prospect needs a technical deep dive, they will ask. You can send documentation after you've established the business reason.

Match the words they used. If they say 'our ops guy,' don't say 'stakeholder.' If they say 'we live in spreadsheets,' use that phrase back. Small language matches make the answer feel written for them, not copied from a feature page. One question at the end is enough. Two questions gives them homework.

- **them:** Does this work with HubSpot?
- **you:** Yes, we connect to HubSpot. Most users do this so their sales team can see lead intent without leaving the CRM, which cuts down on manual data entry during the week. How are you tracking LinkedIn leads in HubSpot today?
- **them:** Mostly just manual entry right now, which is a mess.
- **you:** That's exactly the cleanup we built this for. Would it be worth a 15 minute chat to see how we would automate that for your specific setup?

## Handling the 'no' or 'not yet'

When you don't have the integration they want, don't apologize or promise it's on the roadmap. That makes you look weak or dishonest. Focus on the current way to get the same result. A missing native connection is only a deal-breaker if the manual alternative is impossible.

Show that the workaround is small. 'Export a CSV and drop it into your tool' sounds bad if you leave it there. Add how long it takes and who does it. If the manual step takes 30 seconds once a week, say that. If it takes an hour a day, don't pretend otherwise.

If the integration is genuinely coming, say what exists today and let the buyer decide. Never invent a date. A buyer who hears 'we're building it' without a date can plan around the gap. A buyer who hears a fake date will remember it when the date slips.

When the answer is a hard no, offer the next best path. That might be a CSV import or a one-time migration. If none of those work, say so and end the call politely. A clear no saves both sides time, and it keeps your reputation intact for the next conversation.

| | Scenario | The response |
| --- | --- | --- |
| No native integration, but have an API | We don't have a one-click plug-in for that yet, but we have a REST API that allows your team to pull data into your system automatically. |
| No integration at all | We don't have a direct connection for that tool, but we provide clean CSV exports so you can move your lead lists in seconds. |
| Integration is in development | We're building that now. In the meantime, most users handle this by using our export tool, which takes about a minute to update your records. |

> Never promise a release date for an integration unless you are the product manager and the code is already in staging.

## Doing this with Kinlead

Managing these conversations at scale needs a steady stream of qualified leads. Kinlead finds people on LinkedIn who match the customer you describe, or your website, and scores each lead from 0 to 100 against that profile. Leads below the fit line are not kept.

Replies from every campaign land in one inbox, classified by intent, with interested replies first. You get an email when someone replies. Each campaign can hand the conversation to you at the first reply, so you answer integration questions yourself.

For scripted checks, Kinlead has a REST Agent API and an MCP server, so Claude, ChatGPT, Cursor, or your own scripts can find leads, check replies and draft answers. Pro costs $49 a month after a 7-day free trial. More at [pricing](/pricing) and [demo](/demo).

## Related

- [AI sales playbook for LinkedIn](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)
- [Unified inbox features](https://getkinlead.com/features/unified-inbox.md)
- [Agent API and MCP](https://getkinlead.com/features/agent-api-and-mcp.md)
- [Reply drafting features](https://getkinlead.com/features/reply-drafts.md)

## Common questions

**Should I send a technical PDF in the first reply?**

No. Sending a PDF too early shifts the conversation from a business value discussion to a technical review. Wait until the prospect agrees that the outcome is valuable.

**How do I handle a prospect who insists on a feature list?**

Acknowledge the request, but ask which specific features are required for their current workflow. This forces them to explain the problem they're trying to solve.

**When is the right time to bring in a sales engineer?**

Bring in technical support once the prospect has confirmed that the business outcome is a priority and the only remaining hurdle is the technical implementation.

**What if the prospect goes quiet after I answer?**

Send one follow-up with a concrete example from their workflow, then wait. If they don't reply, mark it closed and move on. Chasing a technical question that was never about the technical details wastes your week.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
