Integration

altaFlow integration

altaFlow (the product formerly named airSlate) automates document workflows: an agent can build templates from PDF or DOCX documents and web forms, define recipient steps, field assignments, conditional jumps and bots, publish template versions, run workflows that pre-fill documents and invite recipients by email or SMS or hand out one-time signing links, read the data recipients filled in, download completed documents as a ZIP, manage organizations, users, groups and webhooks, and read the API request logs. Running a workflow with invites sends them at once. Authentication is OAuth 2.0 (code grant) with an application registered in the altaFlow DevHub dashboard; access tokens last two days and are refreshed. Rate limit: 150 requests per minute per account.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with altaFlow

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.

Document, 9 operations

  • delete_template_documentDelete template documentDELETEDeletes a document from a template. Only possible in an unpublished template.
  • get_template_documentGet template documentGETReturns a document or form of a template with its fields and their data (current unpublished version, else the latest published one).
  • get_version_documentGet version documentGETReturns a document of a specific template version with its fields and their data.
  • get_workflow_documentGet workflow documentGETReturns a workflow document with its fields and the data recipients filled in. Use it to extract submitted data.
  • list_template_documentsList template documentsGETLists the documents and forms of a template (current unpublished version, else the latest published one): id, name, type and dates.
  • list_version_documentsList version documentsGETLists the documents of a specific template version.
  • list_workflow_documentsList workflow documentsGETLists the documents of a workflow's latest revision (a revision is created each time a recipient or bot works on them).
  • prefill_template_documentPrefill template documentPATCHPre-fills a template document with data shared by every future workflow (not for web forms). Each field needs name and value.
  • upload_template_documentUpload template documentPOSTUploads one base64-encoded PDF or DOCX to a template (up to 20 per template). type: PDF, DOC_GENERATION (DOCX with tags) or ONLINE_REDLINING (editable DOCX).

Template, 6 operations

  • create_templateCreate templatePOSTCreates a template (status draft) in an organization. Then add documents with upload_template_document and publish it with publish_template_version before running workflows.
  • delete_templateDelete templateDELETEDeletes a template. Only an unpublished template can be deleted.
  • get_templateGet templateGETReturns a template by id: name, description, draft and published version, redirect URL, tags and dates.
  • list_form_templatesList form templatesGETLists the library of ready-made web forms. Pass a form id as form_template_id to create_web_form to reuse it.
  • list_templatesList templatesGETLists the templates of an organization, optionally filtered by tags. A template is a reusable package of documents and web forms that workflows are run from.
  • update_templateUpdate templatePATCHChanges the redirect URL of a template (unpublished template version only).

Bot, 5 operations

  • attach_template_botAttach template botPOSTAttaches a bot (from list_available_bots) to an unpublished template version, with its conditions and settings.
  • detach_template_botDetach template botDELETEDetaches a bot from an unpublished template version.
  • list_available_botsList available botsGETLists the bots that can be attached to a template through the API (pass a bot id to attach_template_bot).
  • list_template_botsList template botsGETLists the bots attached to the current version of a template, with their conditions and settings.
  • update_template_botUpdate template botPATCHReplaces a template bot's conditions and settings (unpublished template version only). Attributes left out are deleted: read list_template_bots first and send everything back.

Step, 5 operations

  • create_template_stepCreate template stepPOSTCreates a step (a recipient role) in a template, with its access to each document: fill_out, view or hide.
  • delete_template_stepDelete template stepDELETEDeletes a step from a template.
  • list_template_stepsList template stepsGETLists a template's steps (recipients) and their access to each document: fill_out, view or hide (current unpublished version, else the latest published one).
  • list_version_stepsList version stepsGETLists the steps of a specific template version and their access to each document (fill_out, view or hide).
  • update_template_stepUpdate template stepPATCHRenames a step of a template or changes its access to each document: fill_out, view or hide.

Field, 4 operations

  • add_web_form_fieldAdd web form fieldPOSTAdds one fillable field (name and type required) after the existing fields of a web form.
  • delete_web_form_fieldDelete web form fieldDELETEDeletes one field from a web form.
  • get_web_form_fieldGet web form fieldGETReturns one field of a web form with all its attributes.
  • update_web_form_fieldUpdate web form fieldPUTChanges the attributes of one web form field. name and type are required; read get_web_form_field first and send its current values with the change.

Group, 4 operations

  • create_groupCreate groupPOSTCreates a user group in an organization (for a department or a level of responsibility).
  • delete_groupDelete groupDELETEDeletes a user group.
  • list_groupsList groupsGETLists the user groups of an organization with their member count.
  • rename_groupRename groupPATCHRenames a user group.

Member, 4 operations

  • add_group_membersAdd group membersPOSTAdds users (ids from list_users) to a group in one call.
  • list_group_membersList group membersGETLists the members of a user group with their group role.
  • remove_group_memberRemove group memberDELETERemoves a member from a user group.
  • set_group_member_roleSet group member rolePATCHSets a group member's role: ADMIN (sets up group workflows), AUDITOR (reviews workflows) or MEMBER (sends and fills out documents).

Step jump, 4 operations

  • create_step_jumpCreate step jumpPOSTConfigures a jump from one step to another in a template, with its conditions on document fields and its recipient settings.
  • delete_step_jumpDelete step jumpDELETERemoves a jump between steps from a template.
  • list_step_jumpsList step jumpsGETLists the jumps configured between the steps of a template (conditional routing from one step to another).
  • update_step_jumpUpdate step jumpPATCHChanges the conditions and recipient settings of a jump between steps.

User, 4 operations

  • get_userGet userGETReturns one user of an organization: email, name, status and role.
  • list_usersList usersGETLists the users of an organization with their role and status.
  • remove_userRemove userDELETERemoves a user from an organization.
  • update_userUpdate userPATCHChanges a user's role or status (ACTIVE or BLOCKED) in an organization. Leave a field out to keep it.

Webhook, 4 operations

  • create_webhookCreate webhookPOSTSubscribes a callback URL to an event on a workflow, template or organization. The docs describe no signature or secret on deliveries, so treat the callback URL itself as the only check.
  • delete_webhookDelete webhookDELETEDeletes a webhook subscription.
  • get_webhookGet webhookGETReturns one webhook subscription: event, entity and callback URL.
  • list_webhooksList webhooksGETLists the webhooks (event subscriptions) created by the current user in an organization.

Assignment, 3 operations

  • list_document_assignmentsList document assignmentsGETLists which fields of a template document are assigned to which steps (current unpublished version, else the latest published one).
  • list_version_document_assignmentsList version document assignmentsGETLists which fields of a document in a specific template version are assigned to which steps.
  • set_document_assignmentsSet document assignmentsPOSTAssigns fields of a template document to steps (pairs of field_id and step_id). An empty fields list removes every assignment.

Flow, 3 operations

  • get_workflowGet workflowGETReturns a workflow by id: status, signing_status (UNASSIGNED, WAITING, IN_PROGRESS, COMPLETED, REJECTED, FAILED, ON_HOLD), document count and roles with their status.
  • list_workflowsList workflowsGETLists the workflows run from a template, with their status and signing status.
  • run_workflowRun workflowPOSTRuns a workflow from a published template, optionally pre-filling documents. Invites in invites are sent by email or SMS at once; share_links returns one-time links instead.

Tag, 3 operations

  • add_template_tagAdd template tagPOSTAdds a tag (a label used to find templates) to a template.
  • list_template_tagsList template tagsGETLists the tags of a template.
  • remove_template_tagRemove template tagDELETERemoves a tag from a template.

Document placeholder, 2 operations

  • create_document_placeholder_formCreate document placeholder formPOSTCreates a document placeholder form in a template: a slot where a recipient uploads their own document, with optional fillable fields.
  • update_document_placeholder_formUpdate document placeholder formPATCHChanges the name, fields or fillable fields of an existing document placeholder form in a template.

Form, 2 operations

  • create_web_formCreate web formPOSTCreates a web form in a template, from scratch (fields, each with name and type) or from a library form (form_template_id from list_form_templates).
  • update_web_formUpdate web formPUTReplaces a web form's field list: the form keeps only the fields sent. Read get_template_document first and send every field back, changed or not.

Invite, 2 operations

  • invite_usersInvite usersPOSTSends email invitations to join an organization, to registered or unregistered users, at once.
  • invite_workflow_recipientsInvite workflow recipientsPOSTSends invitations to fill out a workflow at once: by email or SMS, one channel per item, per role_id. emails sends to a group of up to 10, first to complete wins.

Log, 2 operations

  • get_api_logGet api logGETReturns one API request log by id (from list_api_logs): URL, method, query, request body, response headers and body, status and whether it was paid. Request headers are left out.
  • list_api_logsList api logsGETLists the API request logs of your applications (app, API type, URL, method, status, paid or not). Filter by app, date range, method or status; page and per_page paginate.

Organization, 2 operations

  • create_organizationCreate organizationPOSTCreates an organization (a workspace in the app). Send name and subdomain, or no field at all for default settings. Returns the new organization id.
  • list_organizationsList organizationsGETLists the organizations (workspaces in the app) the user belongs to. Most other tools need an organization id from here.

Settings, 2 operations

  • get_organization_settingsGet organization settingsGETReturns an organization's settings: recipient registration, completion certificate, eSignature consent, reusable workflows and verified domains.
  • update_organization_settingsUpdate organization settingsPATCHChanges an organization's settings: each setting is true or false, verified_domains is a list of domain names.

Version, 2 operations

  • create_template_versionCreate template versionPOSTCreates a new draft version of a template. Publish the current version first.
  • list_template_versionsList template versionsGETLists the versions of a template (id, version number, status and dates).

Batch, 1 operation

  • run_workflows_batchRun workflows batchPOSTRuns several workflows (20 at most by default) from one template; each item takes the run_workflow body and its invites are sent at once. One result per item, in order; some may fail.

Bot log, 1 operation

  • list_workflow_bot_logsList workflow bot logsGETLists the logs of bot actions in a workflow.

Copy, 1 operation

  • copy_templateCopy templatePOSTCreates a copy of a template under a new name and returns the copy.

Distribute, 1 operation

  • set_template_public_linkSet template public linkPATCHTurns a template's public link on or off. The link can be used any number of times and opens a new workflow for each visitor, filled under the first role.

Download, 1 operation

  • download_workflow_documentsDownload workflow documentsGETDownloads all documents and forms of a workflow as one ZIP archive file.

Link, 1 operation

  • list_workflow_linksList workflow linksGETLists the links created for anonymous signers of a workflow.

Publish, 1 operation

  • publish_template_versionPublish template versionPATCHPublishes a template version so workflows can run from it. Document ids change after publishing a new version: list them again with list_template_documents.

Reject invite, 1 operation

  • cancel_user_invitationCancel user invitationDELETECancels a pending invitation of a user to an organization.

Share, 1 operation

  • create_workflow_linksCreate workflow linksPOSTCreates one-time links to a workflow, one per role (role_id). No email is sent; a link is valid 365 days by default and needs no altaFlow login.

View, 1 operation

  • get_workflow_view_linkGet workflow view linkGETReturns a link that opens the latest revision of a workflow's documents in view-only mode, optionally with download allowed.

Use altaFlow from Claude Code, Cursor or Codex

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

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect altaFlow once

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

altaFlow integration FAQ

What can you do with the altaFlow integration?

LiveContext exposes 82 operations on altaFlow, covering document, template, bot and step.

Popular integrations

Browse the whole catalog