Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

LinkupAPI

LinkupAPI lets agents send messages, manage conversations, and automate outreach across every channel, for sales and recruitment.

CategorySales And Crm
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect LinkupAPI with Flows360

LinkupAPI lets agents send messages, manage conversations, and automate outreach across every channel, for sales and recruitment.

Use the LinkupAPI connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 12 actions and 2 triggers.

Available actions

  • List Accounts
  • Get Account Details
  • Get My Profile
  • Get Profile Info
  • Search People
  • Search Companies
  • Get Company Info
  • Send Message
  • Plus 4 additional declared actions.

Available triggers

  • New Message Received
  • Invitation Accepted

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: LinkupAPI
  • Package: @activepieces/piece-linkupapi@0.1.0
  • Exact artifact digest: sha256:d20f9272b6299be6e8b45746c86c578d69952c1672f6c18178ed01735885221d
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • List Accounts (list_accounts), List all connected LinkedIn accounts linked to your API key. Free (0 credits). Use the returned account_id in other actions. Classification: read.
  • Get Account Details (get_account), Get detailed information and status for a specific connected account. Free (0 credits). Classification: read.
  • Get My Profile (get_my_profile), Retrieve the profile of the connected LinkedIn account. Classification: read.
  • Get Profile Info (get_profile), Retrieve detailed information about a LinkedIn profile by URL, public identifier, or URN. Classification: read.
  • Search People (search_people), Search LinkedIn profiles by keyword, company, title, location, school, industry and more. Returns the LinkedIn URL of each match. Classification: read.
  • Search Companies (search_companies), Search LinkedIn companies by keyword, location, sector and company size. Classification: read.
  • Get Company Info (get_company), Retrieve detailed information about a LinkedIn company page. Classification: read.
  • Send Message (send_message), Send a LinkedIn message to a profile, optionally with a media attachment. Classification: read.
  • Get Conversation (get_conversation), Retrieve the message history of a LinkedIn conversation, by conversation ID or profile URL. Classification: read.
  • Send Connection Request (send_connection_request), Send a LinkedIn connection invitation to a profile, with an optional note. Classification: read.
  • Check Invitation Status (check_invitation_status), Check the status of a connection invitation sent to a profile. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Message Received, webhook.
  • Invitation Accepted, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects14
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
List Accounts Yes No List all connected LinkedIn accounts linked to your API key. Free (0 credits). Use the returned account_id in other actions.
Get Account Details Yes No Get detailed information and status for a specific connected account. Free (0 credits).
Get My Profile Yes No Retrieve the profile of the connected LinkedIn account.
Get Profile Info Yes No Retrieve detailed information about a LinkedIn profile by URL, public identifier, or URN.
Search People Yes No Search LinkedIn profiles by keyword, company, title, location, school, industry and more. Returns the LinkedIn URL of each match.
Search Companies Yes No Search LinkedIn companies by keyword, location, sector and company size.
Get Company Info Yes No Retrieve detailed information about a LinkedIn company page.
Send Message Yes No Send a LinkedIn message to a profile, optionally with a media attachment.
Get Conversation Yes No Retrieve the message history of a LinkedIn conversation, by conversation ID or profile URL.
Send Connection Request Yes No Send a LinkedIn connection invitation to a profile, with an optional note.
Check Invitation Status Yes No Check the status of a connection invitation sent to a profile.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Message Received Yes No webhook trigger declared by the pinned package.
Invitation Accepted Yes No webhook trigger declared by the pinned package.

Setup

Setup

  1. Add the LinkupAPI connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-linkupapi@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 12 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required LinkupAPI connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-linkupapi@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com