Integration

Assembled integration

Assembled is a workforce management platform for support teams. An agent can manage people and their team, queue, site, skill and channel assignments, read and write schedules (activities, activity types, time off requests, working hours), send and edit agent states, push conversation volume, QA scores, forecast totals, adjustments and outliers, read forecasts against actuals, staffing requirements and adherence reports, and use the Assist AI (chat answers, reply drafts, conversation reviews). People, agent states and conversations hold personal data. Each API key is pinned to the API version current when it was created and these tools follow the current reference, so use a recently created key. The deprecated agent state and shift pattern routes and the multipart knowledge article uploads are not exposed. Authentication is HTTP Basic with the API key (sk_live_...) as user name and an empty password.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Assembled

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.

Person, 5 operations

  • create_peopleCreate peoplePOSTCreates one or more people. One person answers with that person, several with a people list. Optionally emails each new person an invitation to Assembled.
  • delete_personDelete personDELETEDeletes a person: a soft delete by default, or a permanent deletion of the person and all associated data with hard=true.
  • get_personGet personGETReturns one person by id: name, email, role, channels, site, teams, queues, skills, platform ids, start and end dates and staffable flag.
  • list_peopleList peopleGETLists people (agents and other users) with optional filters and a name or email search. Returns maps of people, teams and sites keyed by id.
  • update_personUpdate personPATCHUpdates the fields you send on one person; fields you leave out keep their value. Lists you send replace the current list. Returns the updated person in people.

Activity, 4 operations

  • create_activitiesCreate activitiesPOSTCreates several activities in one call; if any fails, none is created. Returns the created activities keyed by id.
  • create_activityCreate activityPOSTSchedules an activity (a shift, break or other activity type) for one agent. Unless allow_conflicts is true it DELETES the agent's overlapping activities.
  • delete_activitiesDelete activitiesDELETEDeletes every activity of the given agents inside a time window; activities crossing the window's edges are cut, not removed.
  • list_activitiesList activitiesGETLists scheduled activities (shifts, breaks, time off and more) in a window of at most 62 days, optionally filtered by team, channel, activity types or agents.

Agent state, 4 operations

  • edit_agent_statesEdit agent statesPOSTInserts, updates or deletes recorded agent states in one call. Deleting or rewriting a state changes adherence reporting.
  • get_agent_state_timelineGet agent state timelineGETReturns agent states in a time window condensed into one non-overlapping timeline per agent; overlaps are resolved by priority_order.
  • list_agent_statesList agent statesGETLists the states of one agent that overlap a time window, with cursor paging (pass next_page_token back as page_token with the same window).
  • send_agent_statesSend agent statesPOSTSends the current state of up to 1000 agents (for example online, away, busy); each agent stays in that state until a new one is sent.

Forecast total, 4 operations

  • create_forecast_totalsCreate forecast totalsPOSTUploads forecast totals: your predicted volume for a time range, which Assembled spreads over its arrival pattern.
  • delete_forecast_totalDelete forecast totalDELETEPermanently deletes one forecast total.
  • get_forecast_totalGet forecast totalGETReturns one forecast total by id, inside a forecasts list.
  • list_forecast_totalsList forecast totalsGETLists uploaded forecast totals (your own volume predictions over a time range) overlapping a window.

Queue, 4 operations

  • create_queuesCreate queuesPOSTCreates one or more queues, each with a name and an optional parent. New queues are associated with every channel enabled in your instance.
  • delete_queuesDelete queuesDELETEDeletes one or more queues by id.
  • list_queuesList queuesGETLists the queues configured on the account (id, name, parent_id), keyed by id. Use the ids to filter people, agents and activities.
  • update_queueUpdate queuePUTRenames a queue and sets its parent: the queue takes exactly the name and parent_id you send.

Site, 4 operations

  • create_sitesCreate sitesPOSTCreates one or more sites, each with a name and an optional parent.
  • delete_sitesDelete sitesDELETEDeletes one or more sites by id.
  • list_sitesList sitesGETLists the sites configured on the account (id, name, parent_id), keyed by id. Use the ids to filter people, agents and activities.
  • update_siteUpdate sitePUTRenames a site and sets its parent: the site takes exactly the name and parent_id you send.

Skill, 4 operations

  • create_skillsCreate skillsPOSTCreates one or more skills, each with a name and an optional parent.
  • delete_skillsDelete skillsDELETEDeletes one or more skills by id.
  • list_skillsList skillsGETLists the skills configured on the account (id, name, parent_id), keyed by id. Use the ids to filter people, agents and activities.
  • update_skillUpdate skillPUTRenames a skill and sets its parent: the skill takes exactly the name and parent_id you send.

Team, 4 operations

  • create_teamsCreate teamsPOSTCreates one or more teams, each with a name and an optional parent.
  • delete_teamsDelete teamsDELETEDeletes one or more teams by id.
  • list_teamsList teamsGETLists the teams configured on the account (id, name, parent_id), keyed by id. Use the ids to filter people, agents and activities.
  • update_teamUpdate teamPUTRenames a team and sets its parent: the team takes exactly the name and parent_id you send.

Activity type, 3 operations

  • create_activity_typeCreate activity typePOSTCreates an activity type, productive (with channels) or time off.
  • delete_activity_typeDelete activity typeDELETEDeletes an activity type by id (from list_activity_types).
  • list_activity_typesList activity typesGETLists the activity types configured on the account (shift, break, time off and more), keyed by id. Use the ids as type_id or activity_type_id.

Forecast adjustment, 3 operations

  • create_forecast_adjustmentsCreate forecast adjustmentsPOSTCreates forecast adjustments (add contacts to, or multiply, a forecast over a window); one invalid entry rejects the batch. Forecasts regenerate in the background.
  • delete_forecast_adjustmentDelete forecast adjustmentDELETEDeletes one forecast adjustment; answers 404 when it does not exist.
  • list_forecast_adjustmentsList forecast adjustmentsGETLists forecast adjustments (manual increases or multipliers on forecasts) filtered by time window, channel and queue.

Forecast outlier, 3 operations

  • create_forecast_outliersCreate forecast outliersPOSTFlags historical windows as outliers so forecasts ignore them; one invalid entry rejects the batch. Forecast models retrain in the background.
  • delete_forecast_outlierDelete forecast outlierDELETEDeletes one forecast outlier; answers 404 when it does not exist.
  • list_forecast_outliersList forecast outliersGETLists forecast outliers (historical windows excluded from forecasting, such as an outage) overlapping a time range.

Time off request, 3 operations

  • cancel_time_off_requestCancel time off requestPOSTCancels an existing time off request.
  • create_time_off_requestCreate time off requestPOSTCreates a time off request for a person. The people in receiver_ids are notified; with evaluate_auto_approval it may be approved at once.
  • list_time_off_requestsList time off requestsGETLists time off requests of every status (approved, pending, canceled, denied) with their updates. Send created_since or updated_since.

Assignment, 2 operations

  • change_person_assignmentChange person assignmentPOSTChanges one attribute of a person (sites, teams, queues, secondary queues, skills, channels or staffable) from a start date, now or scheduled. Early access.
  • list_person_assignmentsList person assignmentsGETReturns a person's sites, teams, queues, secondary queues, skills, channels and staffable status over a time window, one entry per value and period. Early access.

Assignment update, 2 operations

  • list_assignment_updatesList assignment updatesGETLists assignment changes across everyone in your company recorded in a time window, newest first, with cursor paging. Early access.
  • list_person_assignment_updatesList person assignment updatesGETLists one person's assignment changes recorded in a time window, newest first, with cursor paging. Early access.

Assist handoff, 2 operations

  • get_assist_conversation_handoffGet assist conversation handoffGETReturns a handoff summary of an Assist chat conversation by its Assembled id: title, issue, sentiment, summary and transcript, optionally translated.
  • get_assist_response_handoffGet assist response handoffGETReturns a handoff summary of a chat made with create_assist_response: title, issue, sentiment, summary and transcript, optionally translated.

Conversation, 2 operations

  • update_conversationsUpdate conversationsPATCHUpdates existing conversations by import_id, up to 1000 per call; only the fields you send change.
  • upsert_conversationsUpsert conversationsPOSTCreates conversations, or overwrites those with the same import_id, up to 1000 per call. Assembled forecasts from this conversation volume.

Report, 2 operations

  • create_reportCreate reportPOSTStarts generating an adherence, agent ticket stats or agent state handle times report and returns its report_id; read it with get_report until status is complete.
  • get_reportGet reportGETReturns a report requested with create_report: status (in_progress, complete or error) and its metrics per agent, 500 per page by default.

Requirement, 2 operations

  • list_requirementsList requirementsGETLists the manually set required staffing values of fixed requirements in a window of at most 31 days, with scheduled staffing. Automatic requirements are not included.
  • set_requirementSet requirementPOSTSets the required staffing for one interval of an existing fixed requirement (a gated feature). Assembled does not fill intervals you leave empty.

Working hours, 2 operations

  • get_working_hoursGet working hoursGETReturns one working hours rule by id.
  • list_working_hoursList working hoursGETLists the working hours rules: weekly working days, time zone, excluded time and the agent groups each rule is assigned to.

Agent association, 1 operation

  • associate_agentAssociate agentPOSTLinks an agent's identifier on your platform (agent_platform_id) to an Assembled agent, so states sent for it count for that agent. Replaces an existing link.

Agent state edit, 1 operation

  • list_agent_state_editsList agent state editsGETLists the edits made to agent states in a time window: the edited agent, old and new records, the edit itself and who made it (not shown for API edits).

Assist article, 1 operation

  • delete_assist_articleDelete assist articleDELETEDeletes a knowledge article that Assembled uses to generate answers; answers an error when the id is unknown.

Assist conversation, 1 operation

  • list_assist_conversationsList assist conversationsGETLists conversations handled by the Assembled AI agent (chat, email, phone, copilot) with optional messages, workflows, evaluations and experience scores.

Assist reply, 1 operation

  • create_assist_replyCreate assist replyPOSTDrafts a reply to a support case for an agent to review, with rationale, confidence, sources and an optional internal note. Beta, invite only.

Assist response, 1 operation

  • create_assist_responseCreate assist responsePOSTSends a user's chat message to your Assembled AI assistant and returns its answer, cited sources and a handoff recommendation. Creates a chat case.

Event change, 1 operation

  • list_event_changesList event changesGETLists changes made to scheduled events in a time window: who changed what, old and new type, times and channels. Keyed by change id.

Forecast, 1 operation

  • list_forecastsList forecastsGETLists forecasted contact volume per interval for a channel (and optionally a queue) over a time range.

Forecasted vs actual, 1 operation

  • list_forecasted_vs_actualsList forecasted vs actualsGETCompares forecasted and actual metrics per interval for a channel: service level, response and handle times, volumes, occupancy and staffing.

Qa score, 1 operation

  • create_qa_scoresCreate qa scoresPOSTSends quality assurance scores of graded tickets, up to 1000 per call, for Assembled reporting.

Requirement type, 1 operation

  • list_requirement_typesList requirement typesGETLists the requirement types (named sets of staffing requirements, by activity types or by channel and queue), keyed by id.

Role, 1 operation

  • list_rolesList rolesGETLists the roles of your Assembled instance (id, name, description), keyed by role id. Role ids are used by create_people and update_person.

Time off update, 1 operation

  • list_time_off_updatesList time off updatesGETLists changes to time off requests (approve, edit, deny, cancel) since a time, with the requests they concern.

Use Assembled from Claude Code, Cursor or Codex

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

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Assembled once

    Add your Assembled 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.

Assembled integration FAQ

What can you do with the Assembled integration?

LiveContext exposes 72 operations on Assembled, covering person, activity, agent state and forecast total.

Popular integrations

Browse the whole catalog