> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xpander.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Linkup.so

> Linkup.so on xpander: 2 skills, 2 actions in total, how each connects, and which actions to hold for approval.

<Badge color="blue">HTTP API connector</Badge>

## What the skills can do

The platform lists 2 Linkup.so skills, each added to an agent separately. All are HTTP APIs described by OpenAPI specs, not MCP servers:

* **Linkup.so**: 1 actions. Calls carry a credential xpander supplies, so there is nothing to paste.
* **Linkup.so**: 1 actions. Calls carry the credential the connect dialog asks for.

### What the Linkup.so skill can do

API connector: 1 actions, as they appear in the skill panel. 0 of them create, change or delete something in Linkup.so; mark those under **These actions need approval** when you add the skill to an agent.

* **Greeting service** (1): Hello World Greeting Return Hello Message

### What the Linkup.so skill can do

API connector: 1 actions, as they appear in the skill panel. 0 of them create, change or delete something in Linkup.so; mark those under **These actions need approval** when you add the skill to an agent.

* **Greeting service** (1): Hello World Greeting Retrieve Hello World

## Connect Linkup.so

In Xpander Chat, open the agent's settings, click **Add skill**, and search for **Linkup.so**. The connect dialog asks for a connection name and whether the connection is for the **Organization** (one shared account) or **Personal** (your own account, so the agent acts with your permissions where systems allow). On an agent other people use, a personal connection runs their requests as you unless the binding requires each person's own sign-in; see [whose credential a shared agent uses](/use/agents/permissions#whose-credential-a-shared-agent-uses).

Linkup.so connects with **Sign in with Linkup.so**: you authorize in the browser and xpander stores the OAuth token; the agent never sees it, and the token is attached at the moment a skill is called.

## Connect Linkup.so

In Xpander Chat, open the agent's settings, click **Add skill**, and search for **Linkup.so**. The connect dialog asks for a connection name and whether the connection is for the **Organization** (one shared account) or **Personal** (your own account, so the agent acts with your permissions where systems allow). On an agent other people use, a personal connection runs their requests as you unless the binding requires each person's own sign-in; see [whose credential a shared agent uses](/use/agents/permissions#whose-credential-a-shared-agent-uses).

The dialog shows the credential this skill needs and where it goes; the value is stored in the vault and attached at the moment of use.

## Give an agent the Linkup.so skill

Once Linkup.so is connected, any agent you can edit may be given the skill: open the agent's settings, click **Add skill**, and choose **Linkup.so**. Enable only the action groups the agent needs, and mark the actions that should wait for a named person's sign-off under **These actions need approval**. Which skills exist for your organization, and who may add them, is decided by your admins; see [Skills](/use/skills).

## Related Resources

* [Skills](/use/skills)
* [Linkup.so](https://app.linkup.so/)
