Integration

Action Builder integration

Action Builder is the organizing database built with the AFL-CIO for unions and campaigns. List campaigns and their entity types and connection types; list, filter, read, create, update and remove people and other entities (names, addresses, phones, emails: personal data); connect entities to each other and update those connections; list, create and delete tags (info field responses) and read and remove the taggings on records. Creating campaigns, entity types, fields or sections is done in the Action Builder interface only, as the API does not offer it. Authentication is the organization's API key (Admin menu, API and Integrations) sent in the OSDI-API-Token header, plus the organization's actionbuilder.org subdomain.

Connect Action Builder How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Action Builder.Built from the 23 Action Builder tools below, on the connection you add once.

What you can do with Action Builder

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_or_update_personCreate or update personPOSTCreates a person or entity in a campaign, or updates the one matched by its Action Builder identifier, and can add or remove tags and add connections in the same call. Returns the person.
get_personGet personGETReturns one person or entity of a campaign with names, addresses, phones, emails, birth date and latest assessment (personal data). The namespaced fields are in record.
list_peopleList peopleGETLists the people and other entities of a campaign, 25 per page, under _embedded, key osdi:people. Records carry personal data (names, addresses, phones, emails). Narrow with an OData filter.
remove_person_from_campaignRemove person from campaignDELETERemoves a person or entity from the campaign, as removing an entity in the Action Builder interface does.
update_personUpdate personPUTUpdates a person or entity of a campaign. Only the fields sent change. An address, phone or email is updated when matched by its action_builder:identifier or its value, otherwise it is added.

Connection, 4 operations

create_or_update_connectionCreate or update connectionPOSTConnects a person or entity to another existing one in the campaign, or updates that connection, and can add or remove tags on it in the same call. Returns the connection.
get_person_connectionGet person connectionGETReturns one connection of a person or entity, with its type, the other entity's id and whether it is inactive.
list_person_connectionsList person connectionsGETLists the connections of a person or entity in a campaign (links to other people, locals, workplaces), under _embedded, key action_builder:connections.
update_connectionUpdate connectionPUTMarks a connection of a person or entity as inactive or active again.

Tag, 4 operations

create_tagCreate tagPOSTAdds a response to an existing info field of a campaign. The section and field must already exist in the Action Builder interface. Returns the tag.
delete_tagDelete tagDELETERemoves a tag from the campaign. The tagging data collected for it is no longer shown in the interface or the API.
get_tagGet tagGETReturns one tag of a campaign (a response of an info field); its section, field, field type, locked and multiple-responses flags are in record.
list_tagsList tagsGETLists the tags of a campaign, that is the responses of its info fields grouped by section, under _embedded, key osdi:tags, with each field's type and whether it is locked or allows several responses.

Tagging, 4 operations

delete_taggingDelete taggingDELETERemoves a tagging, that is the response from the person or connection it is on.
get_taggingGet taggingGETReturns one tagging (a response on a person or connection record); its section, field, field type and typed response are in record.
list_person_taggingsList person taggingsGETLists the taggings of a person or entity in a campaign (the info field responses on their record), under _embedded, key osdi:taggings.
list_tag_taggingsList tag taggingsGETLists the taggings of one tag, that is every person, entity or connection carrying that response, under _embedded, key osdi:taggings.

Campaign, 2 operations

get_campaignGet campaignGETReturns one campaign with its name, target and organized totals, default entity type and archived flag.
list_campaignsList campaignsGETLists the campaigns of the organization the API key belongs to, 25 per page. Each campaign is under _embedded, key action_builder:campaigns, with its name, target and total numbers and archived flag.

Connection type, 2 operations

get_connection_typeGet connection typeGETReturns one connection type of a campaign and the two entity types it links.
list_connection_typesList connection typesGETLists the connection types of a campaign, each naming the two entity types it links (for example people and locals). They are under _embedded, key action_builder:connection_types.

Entity type, 2 operations

get_entity_typeGet entity typeGETReturns one entity type of a campaign with its singular and plural labels, its naming mode and which standard fields (address, date of birth, email, phone, preferred language) it enables.
list_entity_typesList entity typesGETLists the entity types of a campaign (people and any other kinds of records such as locals or workplaces), with the standard fields each one enables. They are under _embedded, key action_builder:entity_types.

Use Action Builder from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect Action Builder once
Add your Action Builder 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.