# Relay.app e-signature integration

Relay.app agent steps can connect to a remote MCP server, so docuinked works there today. Its human-in-the-loop style fits an approve-then-send flow well.

## What works today

| Route | Status |
|---|---|
| MCP in agent steps | Works now. Relay's docs say agent steps run on Claude models |
| HTTP request step | Works now |
| Listed docuinked integration | Coming soon |

## Set it up

1. Add an agent step to your workflow.
2. Connect a remote MCP server and enter `https://docuinked.com/mcp`.
3. Add your API key as a Bearer credential. Start with a test key.
4. In the step's instructions, say what to prepare and from which template.

## A workflow that fits

1. A trigger fires when a deal is won.
2. An agent step calls `create_from_template` and `send_document`, and returns the `approval_url`.
3. A human step assigns the link to the account lead.
4. The lead approves in docuinked, where the exact draft is on screen.
5. A later step checks `get_document` until the status is `completed`.
6. The workflow files the signed PDF.

Relay's human step is a good place for the link, but it is not what stops the send. The stop is in our server. If someone removes that step, the send still waits for approval.

## Common questions

### Is there a docuinked app in Relay.app?

Not yet, and we found no public request form. MCP does the job today, and a listed app is coming soon.

### Do I still need Relay's human step?

You don't strictly need it, since docuinked holds the send anyway. It is still useful, because it puts the link in front of the right person at the right moment.

### Can a step wait until the document is signed?

Yes. Poll `get_document` in a loop, or start a second workflow from a `document.completed` webhook, which is cleaner for documents that take days.