Integration

Manifestly integration

Manifestly runs recurring checklists and SOPs: start runs from workflow templates, complete, skip, assign and comment on run steps, fill data fields, record approval decisions, list a user's assignments, edit workflow templates (steps, content blocks, data fields), manage Data Tables and holiday calendars, read activity history, departments, roles and team members, and subscribe webhooks. Not exposed: the inbound email that started a run and its attachments, the CSV export (its only output is a download link), and webhook edits (delete and re-create instead); webhook target URLs (outside a workflow template export, which carries the workflow's hooks as stored), avatar images, asset URLs of step content and API self-links are not returned. Authentication: a Manifestly API v2 API key (a master admin creates it under Account Settings, Integrations), sent as Authorization: Bearer <key>. API access is included in every paying plan and in the trial. Calls act as the account and are recorded as its API key, never as a named person. Manifestly's API policy requires OAuth 2.0 for any action that must be attributed to a specific user, including actions an AI agent performs on a user's behalf; this integration offers only the account API key, so it suits account-level automation, not actions that must be credited to a person. Some routes need a feature on the account (business calendars, data tables, approvals) and answer 403 without it; write routes need an admin role in the department concerned. Rate-limited calls answer 429 with a Retry-After header.

Connect Manifestly How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Manifestly

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.

Workflow, 6 operations

archive_workflowArchive workflowPOSTArchives a workflow for real: it CLOSES every scheduled or started run of it and DELETES its scheduled runs. unarchive_workflow does not bring those runs back. Already archived answers 422.
get_workflowGet workflowGETGets one workflow template with its roles and steps (paginated by steps_page and steps_per_page).
import_workflow_templateImport workflow templatePOSTCreates a new workflow for real in a department from a JSON template (as produced by export_workflow_template). Check it first with validate_workflow_template.
list_workflowsList workflowsGETLists workflow templates with id, title, tags, step count and roles. archived=true lists ONLY archived ones (the only way to find one to unarchive). Filter by search, tag or department; paginated.
unarchive_workflowUnarchive workflowPOSTMakes an archived workflow (found with list_workflows archived=true) usable again with its shares. It does NOT reopen the runs archiving closed nor restore deleted scheduled runs.
update_workflowUpdate workflowPATCHUpdates a workflow template's title, description, holiday calendar or business-day rule. Leave out a field to keep it. The calendar keys need their feature (403 without); a locked shared copy is refused with 422.

Workflow step, 6 operations

create_workflow_stepCreate workflow stepPOSTAdds a step or a section to a workflow template (admin of its department). Runs already started keep their steps; only future runs get it. A locked shared copy answers 403, a version-controlled workflow 409.
delete_workflow_stepDelete workflow stepDELETERemoves a step from a workflow template for real (it is deactivated, as in the editor). Deleting a section removes the steps inside it. Runs already started keep their steps.
get_workflow_stepGet workflow stepGETGets one workflow template step with its content, data settings and subtasks; for a section, page and per_page paginate its substeps.
list_workflow_stepsList workflow stepsGETLists a workflow template's steps. Default: top-level steps only; mode=flat or hierarchy lists every step. Paginated with page and per_page (max 100).
reorder_workflow_stepsReorder workflow stepsPATCHReorders a workflow's steps: steps must list every active step exactly once in the new order, a section's steps right after it. Returns the new structure.
update_workflow_stepUpdate workflow stepPATCHEdits a workflow template step; keys left out are kept. Future runs only. A step linked to a step library answers 422 (remove it with delete_workflow_step instead).

Data table, 5 operations

create_data_tableCreate data tablePOSTCreates an empty Data Table in a department the caller administers; add columns with create_data_table_column. A master admin may pass the master account id to share it across departments.
delete_data_tableDelete data tableDELETEDeletes a Data Table for real (soft delete). Refused with 409 while a step data field uses it (in_use on get_data_table).
get_data_tableGet data tableGETGets one Data Table with its columns and whether a step data field uses it (in_use). The id comes from list_data_tables.
list_data_tablesList data tablesGETLists the Data Tables the caller can see (id, name, department, row count, in_use). Needs the data_tables feature. Paginated with page and per_page.
update_data_tableUpdate data tablePATCHRenames a Data Table. Columns are changed with the column tools.

Data table column, 5 operations

create_data_table_columnCreate data table columnPOSTAdds a column to a Data Table. Its internal_key, derived from the name unless given, is the key row cells are written under.
delete_data_table_columnDelete data table columnDELETEDeletes a column for real, and with it every cell of that column in every row.
list_data_table_columnsList data table columnsGETLists a Data Table's columns with id, name, column_type, internal_key (the key row cells use) and position.
reorder_data_table_columnsReorder data table columnsPATCHReorders a Data Table's columns: pass every column id in the new order (ids from list_data_table_columns). Returns the columns with their new positions.
update_data_table_columnUpdate data table columnPATCHRenames a column, changes its type or moves it. Leave out a field to keep it.

Data table row, 5 operations

bulk_write_data_table_rowsBulk write data table rowsPATCHCreates and updates up to 1000 rows in one transaction: a row with an id is updated, one without is created, rows left out are untouched. Any failure writes nothing; row_errors gives its 1-based position.
create_data_table_rowCreate data table rowPOSTAdds one row to a Data Table. cells is keyed by column internal_key (from list_data_table_columns); unknown keys are silently ignored.
delete_data_table_rowDelete data table rowDELETEDeletes one row of a Data Table for real. The row id comes from list_data_table_rows.
list_data_table_rowsList data table rowsGETLists a Data Table's rows, each with its id and cells keyed by column internal_key. Paginated with page and per_page.
update_data_table_rowUpdate data table rowPATCHChanges some cells of one row; cells left out are unchanged and unknown keys are silently ignored.

Holiday, 5 operations

create_business_calendar_holidayCreate business calendar holidayPOSTAdds one hand-entered holiday to a calendar (master admin only). A date can appear only once among a calendar's live holidays.
delete_business_calendar_holidayDelete business calendar holidayDELETERemoves one holiday from a calendar for real (master admin only). Regenerating the region never brings a removed date back.
generate_calendar_holidaysGenerate calendar holidaysPOSTAdds a region's public holidays to a calendar as dated rows, from from_year (default this year) through through_year. Dates that exist or were deleted are never overwritten or revived, so re-running is safe.
list_business_calendar_holidaysList business calendar holidaysGETLists a calendar's holidays ordered by date, each with its id, name, date and source region. Any member can read. Use it to find a holiday id before update or delete.
update_business_calendar_holidayUpdate business calendar holidayPATCHRenames or moves one holiday (master admin only). Leave out a field to keep it. Its source region is kept, and the yearly auto-extend never re-stamps an edited year.

Run, 5 operations

close_runClose runDELETECloses a run for real (a soft delete: the run stops being active). update_run with state=started can reopen it.
create_runCreate runPOSTStarts a real, live run of a workflow that its participants and assignees see in Manifestly. Pass workflow_id (from list_workflows); title, due date, tags, role assignments and participants are optional.
get_runGet runGETGets one run with its top-level steps (paginated by steps_page, 10 per page by default, max 50). Section steps come with empty substeps: read them with get_run_step (page=1). Blocked steps refuse actions.
list_runsList runsGETLists runs (checklist instances) with state, due date, progress and participants. Filter by status, workflow, department, tag or search; paginated with page and per_page (max 100).
update_runUpdate runPUTUpdates a run: title, due date, state (completed to finish it, started to reopen it) or participants. Leave out a field to keep it; participants, when sent, REPLACES the whole participant list.

Run step, 5 operations

change_run_step_stateChange run step statePOSTActs on a run step for real: complete, uncomplete, skip, unskip, start, stop, or data (set its value). A locked step answers 422 Run step not applicable: act on blocking_run_step_id first.
create_run_stepCreate run stepPOSTAdds a step to an ad-hoc run (one not following a fixed template), optionally under a section, at a position, assigned and with a due date.
get_run_stepGet run stepGETGets one run step. For a section step pass page (and per_page, default 10, max 50) to receive its substeps: without page substeps is empty. Hidden steps answer 422.
get_run_step_by_step_idGet run step by step idGETGets the run step created from a given workflow template step (step_id from list_workflow_steps), instead of by run step id.
list_run_stepsList run stepsGETLists a run's live steps with completion, due date, assignees and blockers. Default: top-level steps only; mode=flat or hierarchy lists every step. Blocked steps (non-null blocked_kind) refuse actions.

Run step field, 5 operations

batch_set_run_step_fieldsBatch set run step fieldsPOSTSets several data fields of a run step at once (on a section, fields of its substeps too); filled steps auto-complete. Returns a result per field: a file, image or signature field reports status=error.
get_run_step_fieldGet run step fieldGETGets one data field of a run step (definition and current value). The id is the field id from list_run_step_fields.
list_run_step_fieldsList run step fieldsGETLists the data fields of a run step with their definitions and current values; on a section step, fields of all its substeps. Field ids are what update_run_step_field and batch_set_run_step_fields take.
update_run_step_fieldUpdate run step fieldPUTSets the value of one data field on a run step. When every required field has a value the step auto-completes; clearing a required value uncompletes it. File fields refuse a string: use upload_run_step_field.
upload_run_step_fieldUpload run step fieldPUTStores a file in one file, image or signature field of a run step, sent as base64. Over the deployment's size cap it answers 413 with max_bytes. The step auto-completes on its last required field.

Step data setting, 5 operations

create_step_data_settingCreate step data settingPOSTAdds a data field to a workflow step, of a value_format (text, list, number, date, file, ...). value_format_config only applies to list, number and choose_from_data_table.
delete_step_data_settingDelete step data settingDELETEDeletes one data field of a workflow step for real; the step's other fields stay.
get_step_data_settingGet step data settingGETGets one data field definition of a workflow step by id (ids from list_step_data_settings).
list_step_data_settingsList step data settingsGETLists the data fields a workflow step collects (text, list, date, number, file, ...), in order, with ids. A step may have several or none.
update_step_data_settingUpdate step data settingPATCHUpdates one data field of a workflow step. value_format is always required: read it with get_step_data_setting and send it back when unchanged. Other keys left out are kept.

Business calendar, 4 operations

create_business_calendarCreate business calendarPOSTCreates an empty holiday calendar (master admin only); fill it with generate_calendar_holidays or create_business_calendar_holiday, then attach it with update_workflow (business_calendar_id).
delete_business_calendarDelete business calendarDELETEDeletes a holiday calendar for real (soft delete, master admin only). Workflows it is attached to fall back to weekends-only business days.
list_business_calendarsList business calendarsGETLists the account's holiday calendars (id, name, holiday count). Needs the business_calendars feature; any member can read. Paginated with page and per_page.
update_business_calendarUpdate business calendarPATCHRenames a holiday calendar (master admin only). The id comes from list_business_calendars.

Step content block, 4 operations

create_step_content_blockCreate step content blockPOSTAppends a content block to a workflow step: content is HTML for a text block (no Markdown), or the URL of an existing image, file or video. Uploading a file is not possible here.
delete_step_content_blockDelete step content blockDELETEDeletes one content block of a workflow step for real (the row is destroyed, as in the editor); the other blocks stay.
list_step_content_blocksList step content blocksGETLists the content blocks that make up a workflow step's body (text HTML, image, file, video), in order, with ids. Asset URLs are not returned.
update_step_content_blockUpdate step content blockPATCHEdits one content block of a workflow step. content, when sent, replaces the whole block content (send the full new HTML or URL, not a fragment). Leave out a field to keep it.

Webhook, 3 operations

create_webhookCreate webhookPOSTSubscribes a URL for real to a Manifestly event on a workflow, step, run or run step; Manifestly then POSTs there when it fires. Deliveries are signed (SHA256, version 2) with a key managed in Manifestly.
delete_webhookDelete webhookDELETEDeletes a webhook for real: Manifestly stops delivering its events. The id comes from list_webhooks.
list_webhooksList webhooksGETLists the account's active webhooks with id, event, signature version, watched tags and dates (target URLs are not returned).

Department, 2 operations

get_departmentGet departmentGETGets one department with its members (user id, name, email, role, type). The id comes from list_departments.
list_departmentsList departmentsGETLists the departments (accounts) the key can access, with id and name. Filter with search; paginated with page and per_page (max 100).

Run step comment, 2 operations

create_run_step_commentCreate run step commentPOSTPosts a comment on a run step for real; it is visible to everyone on the run.
list_run_step_commentsList run step commentsGETLists the comments on one run step.

User, 2 operations

get_userGet userGETGets one team member with email, name, type and memberships. Admins only, and only for users in a department they administer.
list_usersList usersGETLists team members (people and AI agents) with email, name, type and memberships (membership ids are what assign_run_step takes). Admins only. Filter by search, email, department_id or population.

Workflow field, 2 operations

get_workflow_fieldGet workflow fieldGETGets one workflow field definition; 404 when it does not exist or the caller cannot read it.
list_workflow_fieldsList workflow fieldsGETLists a workflow's run-level field definitions (ids are what update_run_field_values takes). Admin-visibility fields are left out for non-admins.

Workflow template, 2 operations

export_workflow_templateExport workflow templateGETExports a workflow as a JSON template that import_workflow_template accepts. Only an admin of the workflow's department may export (read access alone answers 403).
validate_workflow_templateValidate workflow templatePOSTChecks a JSON workflow template against a department without creating anything; answers 422 with the errors when it is invalid. Read-only.

Activity, 1 operation

list_activitiesList activitiesGETLists the account's activity feed, newest first, for the departments you administer. Defaults to the last 30 days; after and before move the window (echoed as window). Filter by key, user or department.

Activity key, 1 operation

list_activity_keysList activity keysGETLists every activity key Manifestly can record (fixed, same for every account). Use it to check a key before filtering activities: a misspelled key also answers an empty list.

Approval, 1 operation

decide_approvalDecide approvalPOSTRecords a real approval decision on an approval step, with a required comment: approved, rejected (reopens reviewed steps) or retracted. Needs the approvals feature; can_decide on the step predicts approve or reject.

Assignment, 1 operation

list_assignmentsList assignmentsGETLists the actionable run steps assigned to a user, by due date. An API key is no person, so pass user_id (admins only) to read someone's assignments. Filter by state, kind, workflow, run or due dates.

Credential, 1 operation

verify_credentialsVerify credentialsGETChecks the API key works and returns the authenticated identity (authentication_method, user id, email, account). Use it to test a connection.

Role, 1 operation

list_rolesList rolesGETLists roles with their department and members. A role id is what roles_to_users in create_run takes, and members' user_id identify who may fill it. Filter by department_id or search.

Run activity, 1 operation

list_run_activitiesList run activitiesGETLists everything that happened on one run, newest first. Needs admin or user standing in the run's department (a member or limited user gets 403). Filter by key or key[].

Run field value, 1 operation

update_run_field_valuesUpdate run field valuesPATCHWrites run-level field values keyed by workflow field id (from list_workflow_fields). All or nothing: an invalid value rolls back with 422. Fields the caller may not manage are skipped. Returns the readable values.

Run step assignee, 1 operation

assign_run_stepAssign run stepPOSTAssigns a run step for real to a membership (assignee_membership_id from list_users memberships), or unassigns it when left empty; the assignee sees it in Manifestly. The membership must be in the run's department, else 404 Assignee not found.

Run step due date, 1 operation

set_run_step_due_dateSet run step due datePATCHSets or clears the due date of one run step. Send due_at as an ISO 8601 date-time, or an empty string to clear it.

Run step subtask, 1 operation

change_run_step_subtask_stateChange run step subtask statePOSTCompletes or uncompletes one subtask of a run step. Needed before completing a step whose template has subtasks_required, which otherwise answers Complete all required subtasks first.

Run summary, 1 operation

get_run_summaryGet run summaryGETGets a light completion overview of a run: each section with completed, skipped and total counts, and overall progress, without step detail.

Workflow activity, 1 operation

list_workflow_activitiesList workflow activitiesGETLists one workflow template's authoring history, newest first. Workflow-field activity is included only for an admin of the workflow's department. Names in summary are as of the event.

Use Manifestly from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect Manifestly once
Add your Manifestly connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.