# Gumloop e-signature integration

Gumloop connects to any remote MCP server, so docuinked works there today with one URL. No listing is needed for this to work.

## What works today

| Route | Status |
|---|---|
| Custom MCP connector | Works now |
| HTTP call from a flow | Works now |
| Listed docuinked connector | Coming soon |

## Set it up

1. In Gumloop, add a custom MCP connector.
2. Paste `https://docuinked.com/mcp`.
3. Give it your API key as a Bearer credential, or sign in if it offers that. Start with a test key.
4. Ask the flow to call `whoami` and check that the mode is `test`.

## An example flow

A flow reads a signed-off quote from your CRM, picks the right PDF, and calls `create_document` with the customer as signer. It then calls `send_document` with the `draft_hash`. On a live key, that returns an `approval_url`. Have the flow post that link wherever your team works. A person reads the draft and approves. Nothing reaches the customer until then.

Gumloop flows are good at reading messy inputs. That is also why the approval belongs outside the flow. A line of text in an inbound email can steer a model, but it can't approve a draft.

## Common questions

### Does Gumloop need a special docuinked node?

No. Its custom MCP support picks up our tools from the server, so a new tool appears without any change on your side.

### Can a Gumloop flow finish a document without a person?

Not on a live key. Over MCP, sends always need a person, and signing always needs the signer. In test mode a flow can run end to end.

### What should a flow do with the approval link?

Treat it as a message for a person, such as a chat post or a task. The link only works for someone signed in to your account, so sharing it inside your team is fine.