Skip to main content
Connect your n8n workflows to Doconda to convert, create and edit Word, PowerPoint, Excel and PDF files. An AI Agent node uses the remote MCP server as a tool; a workflow without an agent calls the REST API with an HTTP Request node.

Capabilities

  • Create a Word, PowerPoint, Excel or PDF file, or an artifact, from a request or from Markdown with the workflow’s data.
  • Edit a file: only what is asked changes, and get_report lists every change.
  • Convert a file to another format with no AI, for example any file to Markdown so the agent can read it.
  • Read what people saved in an artifact, such as poll votes.

Setup

This integration uses a Doconda API key (from API keys), stored in an n8n Bearer Auth credential. Paste the key without the word Bearer.

As an AI Agent tool

  1. Add an AI Agent node and, on its Tool input, an MCP Client Tool node.
  2. Endpoint: https://api.eu.doconda.com/mcp.
  3. Server Transport: HTTP Streamable.
  4. Authentication: Bearer Auth, with a new credential where you paste your API key.
  5. Tools to Include: All, or only the ones you want (for example create_document).
You can then ask the agent for things like “When an order comes in, generate its invoice as a PDF”. Its answer includes the document’s download links.

With an HTTP request

For workflows without an agent (always the same document, filled with data from the workflow), use an HTTP Request node:
  • Method: POST · URL: https://api.eu.doconda.com/v1/documents
  • Authentication: Bearer Auth with your API key.
  • Body (JSON):
If the document is ready within 120 s, the response is the finished document, with its links in outputs. If it takes longer, the response is a 202 with the document still in progress (status queued or running) and no outputs yet. In that case, loop until it finishes:
  1. Add a Wait node (for example, 15 seconds).
  2. Add an HTTP Request node with GET https://api.eu.doconda.com/v1/documents/{{ $json.id }}.
  3. Add an If node that goes back to the Wait while status is queued or running.
The links are then in outputs; they expire after 5 minutes.

Tools

The MCP Client Tool node exposes the eight Doconda tools; see the tools for what each one does. A failed call returns { "error": "<code>", "message": "…" }, so the agent can correct itself.

Troubleshooting

  • 401 from the endpoint — The credential holds Bearer ak_eu_… instead of the key alone, or the key is invalid.
  • The HTTP response has no outputs — The document wasn’t ready within 120 s and the response is a 202: add the Wait loop above.
  • 402 with insufficient_balance — The project’s balance can’t cover the document: top up in the dashboard.
  • The download link stopped working — File links expire after 5 minutes: request the document again with GET.