Integration

Periodix Actions integration

Periodix Actions runs LinkedIn and Sales Navigator actions through LinkedIn accounts you connect in its dashboard. Run a search from a LinkedIn or Sales Navigator search URL and fetch its results, read full person and company profiles, a person's or company's recent posts, the comments and reactions on a post and an account's 1st-degree connections, check InMail credits, send connection requests, messages and InMails, and build multi-step message sequences and enroll recipients in them. Every action names the connected account (profileId from list_connected_profiles) it runs from, and Periodix paces calls per account. Reads return personal profile data. Not exposed: account sign-up, login and password routes, the health check and the duplicate v2 action routes (the spec documents them identically to v1); the structured people search and its parameter lookup are MCP-only. Authentication is an API key from the Periodix Actions dashboard (API keys page) sent as a Bearer token. Plans are priced per connected LinkedIn account; the pay-as-you-go plan includes 1,000 results a month (get_organization shows the credits left).

Connect Periodix Actions How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Periodix Actions.Built from the 16 Periodix Actions tools below, on the connection you add once.

What you can do with Periodix Actions

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Connected profile, 2 operations

get_connected_profileGet connected profileGETAgents: ask firstReturns one connected LinkedIn account by id: name, provider and connection status (connected, connecting or disconnected).
list_connected_profilesList connected profilesGETAgents: ask firstLists the LinkedIn accounts connected to your organization with their id (the profileId every action needs), name and connection status. Start here.

Action result, 1 operation

get_action_resultGet action resultGETAgents: ask firstReads the result of a search started with start_linkedin_search: status pending, completed (results in output) or failed (error). Call again while pending; searches usually take a few minutes.

Company profile, 1 operation

get_company_profileGet company profilePOSTAgents: ask firstReturns a LinkedIn company profile: name, industry, employee count and range, description, tagline, locations, activities, website and follower count, by public identifier, numeric id or URN.

Connection, 1 operation

list_connectionsList connectionsPOSTAgents: ask firstLists the 1st-degree connections of the connected LinkedIn account itself (personal data), up to 1,000 per page.

Connection request, 1 operation

send_connection_requestSend connection requestPOSTAgents: ask firstSends a LinkedIn connection request (invitation) from the connected account to a real person, optionally with a note of up to 300 characters. The person is notified; this cannot be undone here.

Inmail balance, 1 operation

get_inmail_balanceGet inmail balancePOSTAgents: ask firstReturns the connected account's remaining InMail credits per feature: premium, recruiter and sales_navigator (empty when that feature is not active). Check it before sending InMails with send_message.

Linkedin search, 1 operation

start_linkedin_searchStart linkedin searchPOSTAgents: ask firstStarts a LinkedIn or Sales Navigator search from a search URL (people, companies, posts, jobs, leads, accounts) and returns a resultId at once; read the results with get_action_result.

Message, 1 operation

send_messageSend messagePOSTAgents: ask firstSends a LinkedIn message from the connected account to a real person, reusing the existing conversation if any. With inmail true and a subject, sends a paid InMail instead. It cannot be unsent here.

Organization, 1 operation

get_organizationGet organizationGETAgents: ask firstReturns your Periodix Actions organization: name, account e-mail, subscriptions (plan, status, seats, period end) and credits (monthly granted and remaining, top-up, overdraft).

Person profile, 1 operation

get_person_profileGet person profilePOSTAgents: ask firstReturns a person's full LinkedIn profile (personal data): name, headline, summary, location, work experience, education, skills, languages and certifications, by public identifier or internal id.

Post, 1 operation

list_user_postsList user postsPOSTAgents: ask firstLists the recent posts published by a LinkedIn person or company, one page at a time (up to 100). Pass a person's internal id, or a numeric company id with isCompany true.

Post comment, 1 operation

list_post_commentsList post commentsPOSTAgents: ask firstLists the comments on a LinkedIn post with the full comment text and author details (personal data), up to 100 per page.

Post reaction, 1 operation

list_post_reactionsList post reactionsPOSTAgents: ask firstLists the people who reacted to a LinkedIn post, or to one of its comments with commentId, with author details (personal data), up to 100 per page.

Sequence, 1 operation

create_sequenceCreate sequencePOSTAgents: ask firstCreates a multi-step LinkedIn message sequence: templated messages with delays, an optional sending schedule and an optional connection request first. Sends nothing until recipients are enrolled with enroll_sequence_recipients.

Sequence recipient, 1 operation

enroll_sequence_recipientsEnroll sequence recipientsPOSTAgents: ask firstEnrolls 1 to 500 recipients in a sequence: from then on, its messages (and connection request) are sent to these real people on the sequence schedule, gradually and within each account's sending limits.

Use Periodix Actions from Claude Code, Cursor or Codex

Connect Periodix Actions in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Periodix Actions operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Periodix Actions

Create your workspace
Sign up free. Nothing to install.
Connect Periodix Actions once
Add your Periodix Actions connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.