Who can connect lc.cx for the company?

A company connection is installed by an administrator.

Can I connect lc.cx just for myself?

Anyone can install a personal connection within the plan’s limit and use it in their own conversations.

Do I use my lc.cx account or a company account?

Yours: lc.cx requires an API key, and each person registers their own, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.

Does Skyller do everything on that action list?

The list is what the vendor offers. What the AI uses in your company is what the administrator turned on, for the groups they defined — Skyller never widens the connector's access.

Does an action in lc.cx happen without anyone approving it?

Reads happen within permission. Write actions have a risk level; sensitive ones show a confirmation card before running and are recorded. The company adjusts the classification when needed.

lc.cx does not show up in my company's catalog.

The administrator may have hidden the integration for your company, or the vendor may have discontinued it — in that case it leaves the catalog on the next synchronization, without deleting what was already connected. Talk to whoever administers Skyller in your company.

Integration · Other

lc.cx in Skyller.

Connect lc.cx to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.

Try it free Book a demo

Actions and events

lc.cx

Other

lc.cx provides URL shortening, branded domains, workspaces, tags, click statistics, and QR code generation through its API.

Actions: 10
Events: 0

Source: Composio catalog
Login: API key
Country: Global — no specific country
Actions list: re-read from the vendor every 24 hours
Official site: lc.cx

Description and action names are the ones the vendor publishes, in English; action descriptions are shown summarized. Skyller does not alter that content.

10 ACTIONS

published by the vendor; the company enables only the necessary ones

0 EVENTS

triggers the system can send, when the vendor offers them

API KEY

each person signs in with their own credential, encrypted

APPROVAL BY RISK

sensitive actions show a card before running

Live proof

One request, one query in lc.cx and one approval.

The scene shows the path of a request; the exact actions depend on the functions your company enables in lc.cx.

Input
A team member asks, in the conversation, for something that today requires opening lc.cx — inside their area's space, with their login.
What Skyller does
1. 01Picks, among the enabled functions, a query action and looks the information up in lc.cx with the person's own credential.
2. 02If the request requires writing something in lc.cx, shows the card with what it is about to do and waits for Approve.
3. 03Returns the result in the conversation and records who asked, which action was used and when.
Result
lc.cx stops being an open tab and starts answering inside the conversation — through the functions your company enabled.

What this scene does not promise

The available actions are the ones the vendor publishes for lc.cx; in your company only the functions turned on by the administrator are available.
If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
Being in this catalog does not mean being installed, with a valid login, working in your company.

Illustrative scene with fictitious data; no action is named because the choice depends on the functions your company enables.

Where this helps your work

lc.cx inside the conversation where the work happens.

Three common situations for people who use lc.cx every day. What Skyller does in each one depends on the functions your company turns on.

Needing the information now

“What is recorded in lc.cx about this?”

The person asks in the conversation and Skyller queries lc.cx with their login, through the enabled read functions, and answers with what it found.

System data in the answer

Recording the result

“Log this in lc.cx.”

Creating or changing a record is a write action: Skyller shows the card with what it is about to do and waits for Approve before touching lc.cx.

Action with approval

Administering

“Enable only what this team needs.”

The administrator connects lc.cx once, turns on the necessary functions, restricts them to groups and follows the record of every call.

Function by function, with a record

Actions and events

What the vendor offers in lc.cx.

Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.

Showing 10 of 10

Create Short Link
LC_CX_CREATE_SHORT_LINK
Shorten one destination URL on lc.cx, optionally choosing its path, tags, note, and workspace.
Create Tags
LC_CX_CREATE_TAGS
Create one or more tags in a workspace and return their ids for attaching to short links.
Delete Short Link
LC_CX_DELETE_SHORT_LINK
Permanently delete one short link. Deletion does not restore the monthly creation quota.
Delete Tag
LC_CX_DELETE_TAG
Permanently delete one tag from the selected workspace.
Get Account Context
LC_CX_GET_ACCOUNT_CONTEXT
Return lc.cx plan and short-link quota information together with available domains and workspaces needed to create and route short links.
Get Short Link
LC_CX_GET_SHORT_LINK
Retrieve one short link by its lc.cx link id from the selected workspace.
List Short Links
LC_CX_LIST_SHORT_LINKS
Return one page of recently created short links in the selected workspace, with an offset for the next page when one may exist.
List Tags
LC_CX_LIST_TAGS
Return all tags available in the selected workspace for organizing short links.
Update Short Link
LC_CX_UPDATE_SHORT_LINK
Update a short link's destination, note, or complete tag assignment. tag_ids is the full replacement list; resend current ids to preserve them or [] to clear.
Update Tag
LC_CX_UPDATE_TAG
Update the name or color of one tag in the selected workspace.

Before you start

What your company needs to use lc.cx.

Login: Each person enters their own lc.cx API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs: An administrator connects lc.cx for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions: 10 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan: Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.

Questions from the people who decide