Integration

TemplioniX integration

TemplioniX generates documents and spreadsheets from Liquid templates kept in the TemplioniX Portal. An agent can list templates, read the fields a template expects and a starter JSON payload for it, generate one document (DOCX, PDF, HTML, TXT, or the native format of XLSX, ODT, ODS, Markdown, CSV, TSV and XML templates) as a file, and start bulk jobs that render one document per record into a ZIP archive, then follow those jobs. Templates are uploaded and edited in the Portal, not through this API. Each generation counts against the subscription's API-call allowance. Authentication is a TemplioniX API key sent in the x-functions-key header; an inactive subscription answers 403.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with TemplioniX

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Bulk generation job, 3 operations

  • get_bulk_generation_jobGet bulk generation jobGETAgents: ask firstReturns a bulk generation job: status (Completed when done), start and end times, the temporary zipUrl of the ZIP once completed, a job-level error and the records that failed.
  • list_template_bulk_jobsList template bulk jobsGETAgents: ask firstLists the bulk generation jobs of one template, newest first, each with status, times, zipUrl when completed and failures.
  • start_bulk_generationStart bulk generationPOSTAgents: ask firstStarts a bulk job rendering one document per record of items into a ZIP; returns jobId at once. Poll get_bulk_generation_job until zipUrl appears or the job fails. Each document counts against the allowance.

Document, 1 operation

  • generate_documentGenerate documentPOSTAgents: ask firstRenders one document from a template and JSON data and returns it as a file (DOCX, PDF, HTML, TXT or the template's native format). Counts against the subscription's API-call allowance.

Template, 1 operation

  • list_templatesList templatesGETAgents: ask firstLists the templates of the account, paged: id, name, description, categories and dates. Pass an id as templateId to the other tools.

Template data model, 1 operation

  • get_template_data_modelGet template data modelPOSTAgents: ask firstReturns a starter JSON object with the fields found in a template, ready to fill and pass as data to generate_document. Generates no document.

Template field, 1 operation

  • get_template_fieldsGet template fieldsGETAgents: ask firstReturns the data fields a template uses, inferred from its Liquid expressions: name, JSON path, type, confidence and where each appears. Use it to build the data for generate_document.

Use TemplioniX from Claude Code, Cursor or Codex

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

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect TemplioniX once

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

TemplioniX integration FAQ

What can you do with the TemplioniX integration?

LiveContext exposes 7 operations on TemplioniX, covering bulk generation job, document, template and template data model.

Popular integrations

Browse the whole catalog