Celoxis integration. Manage data, records, and automate workflows. Use when the user wants to interact with Celoxis data.
Celoxis is a project management and resource management software. It's used by medium to large-sized businesses to plan, track, and manage projects, tasks, and resources. It helps with project portfolio management, time tracking, and collaboration.
Official docs: https://www.celoxis.com/doc/
Use action names and parameters as needed.
This skill uses the Membrane CLI to interact with Celoxis. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
Install the Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/cli
membrane login --tenant
A browser window opens for authentication.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with membrane login complete <code>.
membrane search celoxis --elementType=connector --json
output.items[0].element?.id, then:
membrane connect --connectorId=CONNECTOR_ID --json
When you are not sure if connection already exists:
membrane connection list --json
connectionIdWhen you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json
This will return action objects with id and inputSchema in it, so you will know how to run it.
| Name | Key | Description |
|---|---|---|
| List Users | list-users | Retrieve a list of users from Celoxis |
| List Clients | list-clients | Retrieve a list of clients from Celoxis |
| List Time Entries | list-time-entries | Retrieve a list of time entries from Celoxis |
| List Tasks | list-tasks | Retrieve a list of tasks from Celoxis |
| List Projects | list-projects | Retrieve a list of projects from Celoxis |
| Get User | get-user | Retrieve a specific user by ID from Celoxis |
| Get Client | get-client | Retrieve a specific client by ID from Celoxis |
| Get Time Entry | get-time-entry | Retrieve a specific time entry by ID from Celoxis |
| Get Task | get-task | Retrieve a specific task by ID from Celoxis |
| Get Project | get-project | Retrieve a specific project by ID from Celoxis |
| Create User | create-user | Create a new user in Celoxis |
| Create Client | create-client | Create a new client in Celoxis |
| Create Time Entry | create-time-entry | Create a new time entry in Celoxis |
| Create Task | create-task | Create a new task in Celoxis |
| Create Project | create-project | Create a new project in Celoxis |
| Update User | update-user | Update an existing user in Celoxis |
| Update Client | update-client | Update an existing client in Celoxis |
| Update Time Entry | update-time-entry | Update an existing time entry in Celoxis |
| Update Task | update-task | Update an existing task in Celoxis |
| Update Project | update-project | Update an existing project in Celoxis |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json
To pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"
When the available actions don't cover your use case, you can send requests directly to the Celoxis API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpoint
Common options:
| Flag | Description |
|---|---|
-X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
-H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
-d, --data | Request body (string) |
--json | Shorthand to send a JSON body and set Content-Type: application/json |
--rawData | Send the body as-is without any processing |
--query | Query-string parameter (repeatable), e.g. --query "limit=10" |
--pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.