Integration

Siit integration

Siit is an IT and HR service desk (ITSM) for Slack and Microsoft Teams. Create, update, assign, archive and search employee requests (tickets), post messages and private notes, ask for approvals and import past requests; manage users, teams, departments, legal entities, office locations, services, knowledge-base articles, equipment and the SaaS application catalog with its users, instances and access roles; read workflows, approvals and request tags, and define custom integrations and actions that Siit calls. The deprecated generic tag routes are not exposed. Public API access needs a Trial, Standard or Pro plan and a role with the Public API permission; 60 requests per minute per token. Authentication is a personal Siit API key (account settings) sent as a Bearer token; the API acts as the key's owner, with their permissions and request visibility.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Siit.Built from the 102 Siit tools below, on the connection you add once.

What you can do with Siit

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.

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

Request, 9 operations

  • archive_requestArchive requestPATCHArchives a request (no body). Requests outside the API key owner's visibility answer 404.
  • create_requestCreate requestPOSTCreates a request (ticket): title_markdown, submitted_from and requested_by (a user UID) are required; target picks the service. author defaults to the key owner.
  • create_request_from_slackCreate request from slackPOSTCreates a request from Slack Automations data: title and the requester's slack_user_id, plus an optional Slack message link or channel.
  • get_requestGet requestGETReturns one request with status, priority, requester, assignees, service, tags and custom form inputs. Requests outside the API key owner's visibility answer 404.
  • import_requestsImport requestsPOSTImports past requests with their messages in one call (items required). import_source plus external_id make the import idempotent; at most 500 attachments per batch.
  • list_grouped_requestsList grouped requestsGETLists requests with those of a same group collapsed into one requests_group entry; each result has a kind (request or requests_group) and its data. Scoped to the key owner's request visibility.
  • list_requestsList requestsGETLists requests (tickets) the key owner can see, filtered by status, service, requester, assignee, tag, search text or date windows; expand[] returns related objects. Page with page and per_page.
  • unarchive_requestUnarchive requestPATCHRestores an archived request (no body). Requests outside the API key owner's visibility answer 404.
  • update_requestUpdate requestPUTUpdates a request's title, description, priority, status, snooze, assignees, service, tags or custom form inputs; fields left out keep their value. Requests outside the API key owner's visibility answer 404.

Article, 8 operations

  • archive_articleArchive articlePATCHArchives an article (no body).
  • create_articleCreate articlePOSTCreates a knowledge-base article (title, body_markdown or an external_url, category); publish it with publish_article.
  • get_articleGet articleGETReturns one knowledge-base article with its content and settings.
  • list_articlesList articlesGETLists knowledge-base articles with title, category, audience and publication state, page by page.
  • publish_articlePublish articlePATCHPublishes an article so its audience can read it (no body).
  • unarchive_articleUnarchive articlePATCHRestores an archived article (no body).
  • unpublish_articleUnpublish articlePATCHUnpublishes an article (no body).
  • update_articleUpdate articlePUTUpdates an article; fields left out keep their value. author is only honored on create.

User, 8 operations

  • archive_userArchive userPATCHArchives a user (no body).
  • batch_update_usersBatch update usersPATCHUpdates up to 100 users in one call; each row succeeds or fails on its own, and the call is refused only for an invalid payload, an unknown UID or missing rights.
  • create_userCreate userPOSTCreates a user (email required) with HR data: names, job, department, legal entity, office location, manager, teams and dates.
  • get_userGet userGETReturns one user with HR data, organization links and emails.
  • list_usersList usersGETLists employees (users) with job, department, office, manager, teams and dates, page by page.
  • merge_usersMerge usersPATCHMerges user_uid into the user in the path; the merged user is then deleted. Cannot be undone.
  • unarchive_userUnarchive userPATCHRestores an archived user (no body).
  • update_userUpdate userPUTUpdates a user; fields left out keep their value, and metadata keys are merged into the existing ones.

Application, 6 operations

  • archive_applicationArchive applicationPATCHArchives an application (no body).
  • create_applicationCreate applicationPOSTAdds an application to the SaaS catalog (name and app_link required), with owner, status, cost and renewal date.
  • get_applicationGet applicationGETReturns one application with its status, owners, cost, renewal date and lifecycle.
  • list_applicationsList applicationsGETLists the company's SaaS applications (catalog) with status, owner, cost and lifecycle, page by page.
  • unarchive_applicationUnarchive applicationPATCHRestores an archived application (no body).
  • update_applicationUpdate applicationPUTUpdates an application; fields left out keep their value.

Equipment, 6 operations

  • archive_equipmentArchive equipmentPATCHArchives an equipment item (no body).
  • create_equipmentCreate equipmentPOSTAdds an equipment item with category, holder, office location, hardware details and purchase or leasing data.
  • get_equipmentGet equipmentGETReturns one equipment item with its hardware, holder and purchase or leasing data.
  • list_equipmentsList equipmentsGETLists equipment (laptops, phones...) with holder, office location, lifecycle and purchase or leasing data, page by page.
  • unarchive_equipmentUnarchive equipmentPATCHRestores an archived equipment item (no body).
  • update_equipmentUpdate equipmentPUTUpdates an equipment item; fields left out keep their value.

App access role, 5 operations

  • create_app_access_roleCreate app access rolePOSTCreates an access Role on an application (application UID required). Provisioning actions default to a manual task for the app owner; check allowed actions with get_app_access_role_actions_schema.
  • delete_app_access_roleDelete app access roleDELETEDeletes an App Access Role.
  • get_app_access_roleGet app access roleGETReturns one App Access Role with its application, approval policy, duration rules and provisioning actions.
  • list_app_access_rolesList app access rolesGETLists the App Access Roles employees can request for applications, with approval and duration settings, page by page.
  • update_app_access_roleUpdate app access rolePUTUpdates an App Access Role; the application cannot change. Sending provisioning_actions or deprovisioning_actions replaces the whole list; fields left out keep their value.

Custom action, 5 operations

  • archive_custom_actionArchive custom actionDELETEArchives a Custom Action; it is no longer returned nor offered.
  • create_custom_actionCreate custom actionPOSTCreates a Custom Action that calls submit_url with the integration's secret and headers, offered to agents in Siit and to Workflows as configured.
  • get_custom_actionGet custom actionGETReturns one Custom Action with its request template, inputs and outputs.
  • list_custom_actionsList custom actionsGETLists the Custom Actions of a Custom Integration, sorted by name.
  • update_custom_actionUpdate custom actionPUTUpdates a Custom Action; only the fields sent change, and every definition change creates a new version of the action.

Custom integration, 5 operations

  • archive_custom_integrationArchive custom integrationDELETEArchives a Custom Integration and all its Custom Actions; they are no longer returned.
  • create_custom_integrationCreate custom integrationPOSTCreates an active Custom Integration: an external API with its secret and auth method, used by Custom Actions. Needs a role allowed to configure integrations.
  • get_custom_integrationGet custom integrationGETReturns one Custom Integration (its secret is never returned).
  • list_custom_integrationsList custom integrationsGETLists the company's Custom Integrations (APIs Siit calls from Custom Actions), sorted by name. The stored secret is never returned.
  • update_custom_integrationUpdate custom integrationPUTUpdates a Custom Integration; only the fields sent change. Send access_token to rotate the secret.

Department, 5 operations

  • create_departmentCreate departmentPOSTCreates a department; its name goes in value.
  • delete_departmentDelete departmentDELETEDeletes a department.
  • get_departmentGet departmentGETReturns one department (uid, name in value, timestamps).
  • list_departmentsList departmentsGETLists departments (uid and name in value), page by page.
  • update_departmentUpdate departmentPUTRenames a department (new name in value).

Legal entity, 5 operations

  • create_legal_entityCreate legal entityPOSTCreates a legal entity; its name goes in value.
  • delete_legal_entityDelete legal entityDELETEDeletes a legal entity.
  • get_legal_entityGet legal entityGETReturns one legal entity (uid, name in value, timestamps).
  • list_legal_entitiesList legal entitiesGETLists legal entities (uid and name in value), page by page.
  • update_legal_entityUpdate legal entityPUTRenames a legal entity (new name in value).

Office location, 5 operations

  • create_office_locationCreate office locationPOSTCreates a office location; its name goes in value.
  • delete_office_locationDelete office locationDELETEDeletes a office location.
  • get_office_locationGet office locationGETReturns one office location (uid, name in value, timestamps).
  • list_office_locationsList office locationsGETLists office locations (uid and name in value), page by page.
  • update_office_locationUpdate office locationPUTRenames a office location (new name in value).

Team, 5 operations

  • create_teamCreate teamPOSTCreates a team; its name goes in value.
  • delete_teamDelete teamDELETEDeletes a team.
  • get_teamGet teamGETReturns one team (uid, name in value, timestamps).
  • list_teamsList teamsGETLists teams (uid and name in value), page by page.
  • update_teamUpdate teamPUTRenames a team (new name in value).

Approval, 4 operations

  • get_approvalGet approvalGETReturns one approval with its request, approvers and status.
  • list_approvalsList approvalsGETLists approvals across all requests the key owner can access, with status and approvers, page by page.
  • list_request_approvalsList request approvalsGETLists the approvals attached to one request.
  • request_approvalRequest approvalPOSTAsks one or more users to approve a request: the approvers are notified at once with the body_markdown text.

Service, 4 operations

  • create_serviceCreate servicePOSTCreates a service (name required) with description, category, default assignee and SLA rule.
  • get_serviceGet serviceGETReturns one service with its settings.
  • list_servicesList servicesGETLists services (the catalog requests are filed under) with category, default assignee and audience, page by page.
  • update_serviceUpdate servicePUTUpdates a service; fields left out keep their value. SLA rule and audience need permission to manage the service.

Application user, 3 operations

  • add_application_userAdd application userPOSTRecords that a user has access to an application (user_uid required).
  • list_application_usersList application usersGETLists the users who have access to an application, page by page. Users being deprovisioned stay listed (origin status waiting_deprovisioning) until it completes.
  • remove_application_userRemove application userDELETERemoves a user's association with an application.

Application instance, 2 operations

  • create_application_instanceCreate application instancePOSTCreates an instance of an application for a provider (provider and external_id required); answers 409 if that provider and external_id already exist.
  • delete_application_instanceDelete application instanceDELETERemoves an application instance.

Request follower, 2 operations

  • add_request_followersAdd request followersPOSTAdds users as followers of a request (follower_uids required); archived requests answer 404. Requests outside the API key owner's visibility answer 404.
  • remove_request_followerRemove request followerDELETERemoves a follower from a request; archived requests answer 404. Requests outside the API key owner's visibility answer 404.

Request message, 2 operations

  • list_request_messagesList request messagesGETLists a request's conversation events (messages and notes) with sender, content and attachments, page by page.
  • send_request_messageSend request messagePOSTPosts a message on a request: the requester sees it at once (body_markdown required, optional attachments to download).

Request tag, 2 operations

  • get_request_tagGet request tagGETReturns one request tag.
  • list_request_tagsList request tagsGETLists request tags (labels applied to requests), page by page.

Team inbox, 2 operations

  • get_team_inboxGet team inboxGETReturns one team inbox.
  • list_team_inboxesList team inboxesGETLists team inboxes (the queues requests are assigned to), page by page.

Workflow, 2 operations

  • get_workflowGet workflowGETReturns one workflow; archived workflows are not returned.
  • list_workflowsList workflowsGETLists active workflows (automations) of the company, page by page.

App access role actions schema, 1 operation

  • get_app_access_role_actions_schemaGet app access role actions schemaGETReturns the JSON Schema (draft 2020-12) of the provisioning_actions and deprovisioning_actions arrays accepted by create/update_app_access_role, limited to actions available now.

Article category, 1 operation

  • list_article_categoriesList article categoriesGETLists article categories and subcategories; use parent to rebuild the hierarchy, or filter with parent_category or root_only.

Company, 1 operation

  • get_companyGet companyGETReturns the authenticated company: name, slug, email domains, portal access and whether Slack or Microsoft Teams is integrated.

Equipment category, 1 operation

  • list_equipment_categoriesList equipment categoriesGETLists equipment categories (uid eqcat_...) for create_equipment.

Request assignee, 1 operation

  • update_request_assigneeUpdate request assigneePATCHAssigns a request to a team inbox and/or an admin; the admin must belong to that inbox. Requests outside the API key owner's visibility answer 404.

Request note, 1 operation

  • add_request_noteAdd request notePOSTAdds a private note to a request, visible to agents only (body_markdown required).

Request status, 1 operation

  • update_request_statusUpdate request statusPATCHChanges a request's status (open, in_progress, waiting, resolved or archived). Requests outside the API key owner's visibility answer 404.

Use Siit from Claude Code, Cursor or Codex

Connect Siit in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Siit 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 Siit

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Siit once

    Add your Siit connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. 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.

Siit integration FAQ

What can you do with the Siit integration?

LiveContext exposes 102 operations on Siit, covering request, article, user and application.

Popular integrations

Browse the whole catalog