Integration

Quentn integration

Quentn is a marketing automation platform (contacts, tags, campaigns). Create contacts one by one or in bulk with duplicate checking, read a contact by ID or email with chosen fields, update or delete it, add or remove its terms (tags), add, edit and remove contact comments, put a contact into a campaign at a trigger element, manage terms and custom contact fields, and read the system's users. This uses Public API version 1 (the default); version 3, still in beta, and its pipelines, opportunities and emails are not covered. Authentication is an API key sent as a Bearer token; the host is your system's own, https://<system id>.<server id>.quentn.com.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Quentn

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, 6 operations

  • create_contactCreate contactPOSTCreates a contact, merging with a duplicate when one is found (duplicate_check_method, duplicate_merge_method). Returns its id plus any return_fields.
  • create_contactsCreate contactsPOSTCreates several contacts in one request with the same duplicate handling as create_contact. Returns one entry per contact (id and mail, or error and message for a failed one).
  • delete_contactDelete contactDELETEPermanently deletes a contact. Irreversible.
  • get_contactGet contactGETReturns a contact by ID. Without fields only id, first_name, family_name and mail are returned; list other built-in or field_ custom fields in fields.
  • get_contact_by_emailGet contact by emailGETReturns the contacts with this email address, always as a list (several contacts can share one address). Without fields each entry has only id, first_name, family_name and mail; list other fields in fields.
  • update_contactUpdate contactPUTUpdates a contact: send only the fields to change (built-in fields or field_ custom fields) in contact; add return_fields to get fields back.

Custom field, 6 operations

  • create_custom_fieldCreate custom fieldPOSTCreates a custom contact field of a given field_type with a label; returns its field_name and field_id.
  • delete_custom_fieldDelete custom fieldDELETEDeletes a custom contact field and its values. Irreversible.
  • get_custom_fieldGet custom fieldGETReturns a custom contact field by its numeric ID.
  • get_custom_field_by_nameGet custom field by nameGETReturns a custom contact field by its machine name (field_...).
  • list_custom_fieldsList custom fieldsGETLists all custom contact fields with field_id, machine field_name (field_...), label, type and whether required.
  • update_custom_fieldUpdate custom fieldPUTUpdates a custom contact field (label, description, size, options, limits, texts). Only sent fields change.

Term, 6 operations

  • create_termCreate termPOSTCreates a term (tag) with a name and optional description and returns its id.
  • delete_termDelete termDELETEDeletes a term (tag). Irreversible.
  • get_termGet termGETReturns a term (tag) by ID.
  • get_term_by_nameGet term by nameGETReturns a term (tag) by its exact name.
  • list_termsList termsGETLists all terms (tags) of the system with id, name, description and whether deletion is blocked. Paged by offset and limit (default 500).
  • update_termUpdate termPUTRenames a term (tag) or changes its description. Leave a field out to keep it.

Contact comment, 4 operations

  • add_contact_commentAdd contact commentPOSTAdds a text comment to a contact and returns its comment_id.
  • delete_contact_commentsDelete contact commentsDELETEDeletes comments of a contact. Pass the comment IDs in ids, separated by a pipe, e.g. 5|6. Irreversible.
  • list_contact_commentsList contact commentsGETLists a contact's comments, paged by range (0-based page) and limit (max 50), sorted asc or desc.
  • update_contact_commentUpdate contact commentPUTReplaces the text of one comment of a contact (id from list_contact_comments).

Contact term, 3 operations

  • add_contact_termsAdd contact termsPUTAdds terms (tags) to a contact from a list of term IDs (from list_terms); terms the contact already has are kept. Use remove_contact_terms to take terms off.
  • list_contact_termsList contact termsGETLists the terms (tags) assigned to a contact, with id, name and description.
  • remove_contact_termsRemove contact termsDELETERemoves terms (tags) from a contact. Pass the term IDs in ids, separated by a pipe, e.g. 123|555.

User, 3 operations

  • get_userGet userGETReturns a Quentn system user by ID.
  • get_user_by_emailGet user by emailGETReturns a Quentn system user by email address.
  • list_usersList usersGETLists the Quentn system's users (staff accounts), paged by range (0-based) and limit (max 20).

Campaign contact, 1 operation

  • add_contact_to_campaignAdd contact to campaignPOSTPuts a contact into a campaign at a trigger element: this starts the campaign's automation, which can email the contact, so confirm with the user first. Identify it by id, mail, or name and full address; sent fields overwrite stored ones.

Use Quentn from Claude Code, Cursor or Codex

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

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Quentn once

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

Quentn integration FAQ

What can you do with the Quentn integration?

LiveContext exposes 29 operations on Quentn, covering contact, custom field, term and contact comment.

Popular integrations

Browse the whole catalog