Use case · n8n
Form to LinkedIn invitation in three nodes
A Typeform lands, an HTTP node calls the invitation endpoint with a personal note, a Slack node confirms the send.
Form received, Invitation sent, Slack notified
what linkupapi allow you to do
Connect LinkedIn, email and WhatsApp to n8n, Make or Zapier. Send invitations and messages, find emails and enrich profiles from a no-code workflow.
Built for autonomous workflows and agentic systems. Seamlessly integrate our API into AI agents for intelligent B2B automation at scale.
Reach prospects across LinkedIn, WhatsApp, email, and web. Manage all B2B channels through one unified API platform.
Aggregate information from dozens of public sources. Get the most complete profiles by combining data from multiple sources.
Connect with your favorite tools through native integrations. Compatible with Make, n8n, Zapier, and any platform via REST API.
Never store credentials or post-login data. EU-hosted, GDPR and CCPA compliant, with a data processing agreement on request.
Add LinkedIn connection requests, messaging, and engagement features to your platform. Let your users automate outreach without leaving your interface.
// What it does
LinkupAPI is a plain REST API with one header, so every action fits in an HTTP Request node. Trigger it from a form, a CRM event or a schedule, and receive replies through a webhook node.
// Three workflows teams ship with it
Use case · n8n
A Typeform lands, an HTTP node calls the invitation endpoint with a personal note, a Slack node confirms the send.
Form received, Invitation sent, Slack notified
Use case · Make
A new contact triggers a reverse email lookup and a profile fetch; the fields are written back to HubSpot.
Contact created, Profile fetched, HubSpot updated
Use case · Zapier
A LinkupAPI webhook fires on every reply; a Zap tags the lead in the CRM and pauses the sequence.
Reply received, Lead tagged, Sequence paused
// Two calls, one sequence
1# HTTP Request node (n8n) — same body in Make or Zapier
2POST https://api.linkupapi.com/v2/network
3Headers:
4 x-api-key: YOUR_API_KEY
5 Content-Type: application/json
6Body (JSON):
7{
8 "account_id": "YOUR_ACCOUNT_ID",
9 "action": "invite",
10 "params": {
11 "profile_url": "{{ $json.linkedin_url }}",
12 "message": "Hi {{ $json.first_name }}, thanks for signing up. Happy to connect!"
13 }
14}
n8n workflow
Form → LinkupAPI → Slack
// How it compares
Your users trust you with their accounts. Here is how we keep them safe.
Passwords never stored
We never keep your users' passwords. Sessions are encrypted, isolated per account and revocable at any time.
EU-hosted, GDPR & CCPA
Data is processed and hosted in the European Union. GDPR and CCPA compliant, with a data processing agreement on request.
Google-verified security
LinkupAPI passed Google's CASA security assessment and is a verified Gmail app. Same review, same standards for every channel.
Enterprise-grade security measures ensuring your data remains protected at every step of the process.
Is there an n8n node for LinkupAPI?
Use the HTTP Request node with the x-api-key header; every endpoint is a POST with a JSON body. The same body works in Make's HTTP module and in Zapier's Webhooks step.
How do I receive replies in n8n?
Create a LinkupAPI webhook once, pointing at an n8n Webhook node. Accepted invitations, new messages and bounces arrive as JSON, with retries and a delivery log.
Can I send emails and WhatsApp messages too?
Yes. Email and WhatsApp use the same seat model and the same body shape, so a multi-channel sequence is one workflow with three HTTP nodes.
How do I stay within LinkedIn limits from a workflow?
The API paces every action per seat and returns an explicit error at the limit. Keep the notes personal and add a delay node between sends if you batch.
Do I need a developer?
No. A workflow builder with the endpoint URL and the API key is enough. The API reference gives the body for each action.
LinkedIn, email and WhatsApp through one API. Unlimited accounts, one fixed price.
Endpoints
Uptime
Avg Response