Integration

Adversus integration

Adversus is an outbound call center dialer and CRM. Manage campaigns, leads, contacts and contact persons, lead pools, users, teams, products and sales, read call sessions, calls, SMS, notes, appointments and email activity, configure custom fields and field mappings, and register webhooks for dialer events. Bulk imports (whose vendor routes are malformed in the spec), the JSON-lines workforce report, the call-recording redirects, the recording-clips list (declared as JSON lines; list_recordings returns clips with their recordings) and the deprecated call detail record routes are not exposed. Authentication is HTTP Basic with the username and password of an API user created in Adversus. Rate limits: 1000 requests per hour, 60 per minute, 2 concurrent.

Connect Adversus How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Adversus

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.

Contact, 5 operations

create_contactCreate contactPOSTCreate a contact by specifying the pool and data-entries.
delete_contactDelete contactDELETEDeletes the contact specified
get_contactGet contactGETReturns the non-empty data-entries for a given contact id
list_contactsList contactsGETLists contacts matching a filter given as a query parameter (the same filter as find_contacts_by_data). Without a projection only the contact ids are returned.
update_contactUpdate contactPATCHPatches the data-entries for a given contact, by specifying a key-value map with the fields that should be altered

Field mapping, 5 operations

create_field_mappingCreate field mappingPOSTCreate a new mapping between adversus field IDs and external IDs. The mappings can be used to return an external ID of a field instead of Adversus internal ID
delete_field_mappingDelete field mappingDELETEDeletes a field IDs mapping
get_field_mappingGet field mappingGETReturns the information about a specific fields mapping.
list_field_mappingsList field mappingsGETReturns all the existing mappings of external field IDs.
update_field_mappingUpdate field mappingPUTUpdates a field IDs mapping

Lead, 5 operations

create_leadCreate leadPOSTThis endpoint creates a new lead.
delete_leadDelete leadDELETEThis endpoint deletes a single lead.
get_leadGet leadGETReturns information about a specific lead.
list_leadsList leadsGETThe lead endpoint returns information about the leads related to the authenticated user.
update_leadUpdate leadPUTThis endpoint updates a single lead.

Product, 5 operations

create_productCreate productPOSTCreate a new Product.
delete_productDelete productDELETEDeleting an existing product. Can't delete a product with an active addon.
get_productGet productGETReturns information about a specific product.
list_productsList productsGETReturns a list of products for an authenticated client.
update_productUpdate productPATCHUpdate an existing product.

User, 5 operations

create_userCreate userPOSTCreate a regular (aka. internal) user belonging to the authenticated client.
deactivate_userDeactivate userDELETEDeactivates the user with the given id (Adversus does not remove it).
get_userGet userGETThe user endpoint returns information about a particular user. The response includes the display name and other details about each user.
list_usersList usersGETThe user endpoint returns information about all the users related to the authenticated user. The response includes the display name and other details about each user.
update_userUpdate userPATCHUpdates a regular (aka. internal) user belonging to the authenticated client.

Webhook, 5 operations

create_webhookCreate webhookPOSTRegisters a webhook: Adversus posts the chosen event (lead_saved, call_ended, sms_received...) to your url. For lead_saved a template can reshape the posted data with [fieldId] merge-tags.
delete_webhookDelete webhookDELETEThis endpoint deletes a single webhook.
get_webhookGet webhookGETReturns information about a specific webhook.
list_webhooksList webhooksGETThe webhooks endpoint returns information about all the webhooks related to the authenticated user.
update_webhookUpdate webhookPUTThis endpoint updates a single webhook.

Campaign field, 4 operations

create_campaign_fieldCreate campaign fieldPOSTCreates a new campaign field, returns array of campaign fields
get_campaign_fieldGet campaign fieldGETReturns information about a specific campaign field
list_campaign_fieldsList campaign fieldsGETReturns list of campaign fields
update_campaign_fieldUpdate campaign fieldPUTUpdates a campaign field

User field, 4 operations

create_user_fieldCreate user fieldPOSTCreates a new user field, returns array of user fields
get_user_fieldGet user fieldGETReturns information about a specific user field
list_user_fieldsList user fieldsGETReturns list of user fields
update_user_fieldUpdate user fieldPUTUpdates a user field

Contact person, 3 operations

create_contact_personCreate contact personPOSTCreate a contact person and add the related data.
delete_contact_personDelete contact personDELETEDelete a contact person.
update_contact_personUpdate contact personPATCHUpdate the data relation for a contact person.

Pool, 3 operations

create_poolCreate poolPOSTCreate a new lead pool belonging to the authenticated user.
get_poolGet poolGETReturns information about a pool.
list_poolsList poolsGETThe pools endpoint returns information about all the lead pools related to the authenticated user.

Add contact, 2 operations

add_campaign_contactAdd campaign contactPOSTAdds a contact to a specific campaign (making it a campaign-lead), specifying a lead status indicating the contacts campaign state (e.g. not previously dialed)
add_campaign_contactsAdd campaign contactsPOSTAdds several contacts to a campaign in one call, like add_campaign_contact but with a list of contacts, each with its initial campaign status.

Campaign, 2 operations

get_campaignGet campaignGETReturns information about a specific campaign.
list_campaignsList campaignsGETThe campaign endpoint returns information about the campaigns related to the authenticated user. The response includes the display name and other details about each campaigns.

Data, 2 operations

update_campaign_dataUpdate campaign dataPATCHUpdates data values in specified field ids. The key representing campagin field Id, and value representing the new value for the field
update_user_dataUpdate user dataPATCHUpdates data values in specified field ids. The key representing campagin field Id, and value representing the new value for the field

Efficiency, 2 operations

get_campaign_efficiencyGet campaign efficiencyGETReturn efficiency on a campaign to see what time is being used for.
get_user_efficiencyGet user efficiencyGETThis endpoint is used for retrieving details on user efficiency, e.g. time spend waiting for calls vs time spent in calls vs time spenting processing calls

Field, 2 operations

list_contact_person_fieldsList contact person fieldsGETGet a list of contact person fields
list_fieldsList fieldsGETThe fields endpoint returns information about all the data fields related to the authenticated user.

Note, 2 operations

get_noteGet noteGETReturns information of a specific note
list_notesList notesGETReturns notes of the leads, optionally filtered and/or by a query parameter

Project, 2 operations

get_projectGet projectGETEndpoint for details about a particular project along with the associated campaigns
list_projectsList projectsGETEndpoint for getting all projects for the authenticated client

Sale, 2 operations

get_saleGet saleGETReturns information about a specific sale.
list_salesList salesGETReturns the list of sales

Session, 2 operations

get_sessionGet sessionGETReturns information about a specific session.
list_sessionsList sessionsGETThe lead endpoint returns information about the sessions related to the authenticated user.

Sms, 2 operations

get_smsGet smsGETReturns information of a specific text message
list_smsList smsGETReturns information of registered in- and outbound text messages, optionally filtered by a query parameter

Activity, 1 operation

list_mail_activityList mail activityGETThe mail activity endpoint returns information about all the mails sent.

Appointment, 1 operation

list_appointmentsList appointmentsGETThe appointments endpoint returns information about all the appointments (bookings) related to the authenticated user.

Bulk, 1 operation

bulk_contact_person_actionsBulk contact person actionsPOSTQueues create, update and delete actions on contact persons in one call; the result is posted to your callback URL when processed. Answers code and status (queued).

Call, 1 operation

list_callsList callsGETThis endpoint is used for retrieving billing information about phone calls

Contacts external, 1 operation

update_contact_externalUpdate contact externalPATCHPatches the data-entries for a given contact, by specifying a key-value map with the fields that should be altered

Find by data, 1 operation

find_contacts_by_dataFind contacts by dataPOSTFinds contacts whose data matches a filter on field ids (only $eq and $in) and returns the matching contact ids; read one with get_contact.

Group, 1 operation

list_groupsList groupsGETThe groups endpoint returns a list of all user groups created. User groups are used inside for grouping multiple users in the analytics module.

Login session, 1 operation

list_login_sessionsList login sessionsGETThis endpoint is used for retrieving details on user login session

Login time, 1 operation

get_user_login_timeGet user login timeGETThis endpoint is used for retrieving details on user efficiency, e.g. time spend waiting for calls vs time spent in calls vs time spenting processing calls

Organization, 1 operation

get_organizationGet organizationGETReturns an unique identifier, and the name for the organization which the API user belongs to.

Pause reason, 1 operation

list_pause_reasonsList pause reasonsGETReturns the pause reasons configured for the authenticated client, to resolve a pause reason id into a human readable name.

Person, 1 operation

list_contact_personsList contact personsGETGet the contact persons with their current data

Recording, 1 operation

list_recordingsList recordingsGETReturns recordings and recording-clips ordered by, and optionally filtered by upload time. This is the recommended way to export recordings to a media archive.

Role, 1 operation

list_rolesList rolesGETThe roles endpoint returns a list of all roles created. Roles are currently known as permission groups inside Adversus and are used to assign a set of capabilities for a user.

Segment, 1 operation

list_campaign_segmentsList campaign segmentsGETGet a list of active campaign segments from a campaign

Team, 1 operation

list_teamsList teamsGETLists the teams. Teams control which campaigns users can access; a user is assigned to teams through its memberOf property (see get_user).

Transcription summary, 1 operation

list_transcription_summariesList transcription summariesGETReturns a list of transcription summaries

Use Adversus from Claude Code, Cursor or Codex

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

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