# Paperless Post API and MCP server

> Paperless Post has no public API (checked 10 Oct 2026). Guest lists, sending, RSVPs and messages live only in the website and apps, and guest lists and RSVPs move in and out as CSV files.

Online invitations and cards: hosts send a Card or Flyer by email, text or link, then track RSVPs and message guests.

## What is the Paperless Post API?

Cotlet's Paperless Post API exposes 11 endpoints for your own Paperless Post account: list events, get event, list guests, get guest, export guest list, list contacts, add guests, send invitation, send message, send private message and tag guests. The list_events endpoint returns your Cards and Flyers from My Events, with type, date and send status. Each endpoint takes simple JSON inputs like event_id, status or cursor and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities)
- **Endpoints:** 11 (6 read, 5 write)
- **Updated:** 2026-10-10

Paperless Post has no public API (checked 10 Oct 2026). Cotlet is a hosted MCP server and REST API for Paperless Post with 11 endpoints (6 read, 5 write): your AI agent signs in as you and does the work.

## Does Paperless Post have an official API?

Paperless Post has no public API (checked 10 Oct 2026). Guest lists, sending, RSVPs and messages live only in the website and apps, and guest lists and RSVPs move in and out as CSV files.

| Task | Paperless Post official | Cotlet |
|---|---|---|
| List your events and drafts | No | Yes |
| Add guests to an invitation | Partly: Spreadsheet upload in the website, no API | Yes |
| Send or schedule an invitation | No | Yes |
| Read RSVPs and guest statuses | Partly: CSV export from the Tracking page, no API | Yes |
| Send reminders and broadcasts | No | Yes |
| Message one guest privately | No | Yes |
| Tag guests | No | Yes |

Sources: [Does Paperless Post offer any integrations? (Help Center)](https://paperlesspost.zendesk.com/hc/en-us/articles/52828810876571-Does-Paperless-Post-offer-any-integrations), [Exporting your Tracking page and RSVPs (Help Center)](https://paperlesspost.zendesk.com/hc/en-us/articles/4408189170075-Exporting-Your-Tracking-Page-and-RSVPs-and-Transferring-Your-Unsent-Guest-List), [Send an RSVP reminder or follow up message (Help Center)](https://paperlesspost.zendesk.com/hc/en-us/articles/4408189210779-Send-an-RSVP-reminder-or-follow-up-message-to-guests-or-recipients), [Does Paperless Post resend unopened emails? (Help Center)](https://paperlesspost.zendesk.com/hc/en-us/articles/360043312171-Does-Paperless-Post-resend-unopened-emails-Does-Paperless-Post-automatically-send-reminders), [Organize guests with Guest Tags (Help Center)](https://paperlesspost.zendesk.com/hc/en-us/articles/14806744832795-Organize-Guests-with-Guest-Tags), [Upload a spreadsheet of contacts to your guest list (Help Center)](https://paperlesspost.zendesk.com/hc/en-us/articles/206579093-Can-I-upload-a-spreadsheet-of-contacts-to-create-my-guest-or-recipient-list-)

## For AI agents

```text
Paperless Post has no public API (checked 10 Oct 2026). Guest lists, sending, RSVPs and messages live only in the website and apps, and guest lists and RSVPs move in and out as CSV files.
Cotlet provides a hosted MCP server and REST API for Paperless Post: 11 tools (6 read, 5 write).
Access       Request access at https://cotlet.dev/app/signup?app=paperless-post; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/paperless-post
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_events, get_event, list_guests, get_guest, export_guest_list, list_contacts, add_guests, send_invitation, send_message, send_private_message, tag_guests
Confirm      send_invitation, send_message, send_private_message (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/paperless-post-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=paperless-post (Paperless Post is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Paperless Post once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Paperless Post server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Paperless Post in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Paperless Post's terms; Cotlet is not affiliated with Paperless Post.
```

## What can an AI agent do in Paperless Post?

Cotlet is best for hosts and event planners who want an agent to load guest lists, chase RSVPs and message guests without running or fixing a server.

- **[Send RSVP reminders to guests who have not replied](https://cotlet.dev/integrations/paperless-post-api-mcp-server/send-rsvp-reminders)** (runs: weekly): "Every Monday until the RSVP deadline, check the Summer Gala in Paperless Post, give me the headcount, and send a Reminder to RSVP to everyone who has not answered and was not reminded in the last 5 days. List anyone who bounced or unsubscribed so I can reach them myself." → `list_events`, `list_guests`, `get_guest`, `send_message`, `export_guest_list`
- **[Send invitations from a spreadsheet](https://cotlet.dev/integrations/paperless-post-api-mcp-server/send-invitations-from-spreadsheet)**: "Take guests.xlsx from my planner, clean it up for Paperless Post (one contact per guest, families as groups, plus-ones in Total Invited), add everyone to the unsent list of my "Summer Gala" Card and schedule it for Friday at 9:00 New York time. Show me the rows you had to fix first." → `list_events`, `list_guests`, `list_contacts`, `add_guests`, `send_invitation`
- **Export RSVPs to a spreadsheet** (runs: weekly): "Give me the current RSVP list for Saturday as a CSV and tell me how many are attending." → `list_events`, `list_guests`, `export_guest_list`
- **Announce a time or location change**: "The venue changed. Tell everyone attending about the new address." → `get_event`, `send_message`
- **[Tag guests and message each group](https://cotlet.dev/integrations/paperless-post-api-mcp-server/tag-guests-and-message-groups)**: "Here are the out-of-town guests from my wedding planner sheet. Tag them "lodging" in Paperless Post, then send the ones who are attending the hotel room block link, and tell me who on the sheet is not on the guest list." → `list_guests`, `tag_guests`, `get_event`, `send_message`, `send_private_message`

## Can Paperless Post automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Paperless Post connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to send rsvp reminders to guests who have not replied, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/paperless-post/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/paperless-post/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/paperless-post/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/paperless-post/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Paperless Post.

### list_events

Your Cards and Flyers from My Events, with type, date and send status. Access: read. REST: `POST /api/v1/paperless-post/list_events`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | draft, sent or scheduled. Default: sent. |
| `limit` | integer | no | Number of events to return. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the Cards and Flyers on your account, newest first. Use the event_id of each item in the other endpoints. Drafts have no guests sent yet.

Example response:

```json
{
  "events": [
    {
      "event_id": "ev_8F3K2Q",
      "title": "Summer Gala",
      "type": "card",
      "status": "sent",
      "event_date": "2026-10-17T19:00:00-04:00"
    },
    {
      "event_id": "ev_2M9X1B",
      "title": "Baby shower",
      "type": "flyer",
      "status": "draft",
      "event_date": "2026-11-08T14:00:00-05:00"
    }
  ],
  "next_cursor": null
}
```

### get_event

Event details: title, host, date, time, location and the design type. Access: read. REST: `POST /api/v1/paperless-post/get_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Card or Flyer ID from list_events. |

Returns what guests see on the invitation: title, host name, date and time, time zone and location. Use it before a time or location message so the text matches the invitation.

Example response:

```json
{
  "event_id": "ev_8F3K2Q",
  "title": "Summer Gala",
  "type": "card",
  "host": "Dana Whitfield",
  "event_date": "2026-10-17T19:00:00-04:00",
  "location": "The Boathouse, 12 Pier Road",
  "status": "sent"
}
```

### list_guests

The Tracking page: each guest or group with status, number attending and Guest Tags. Access: read. REST: `POST /api/v1/paperless-post/list_guests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Card or Flyer ID from list_events. |
| `status` | string | no | Only guests with this status as shown on the Tracking page, for example attending. |
| `tag` | string | no | Only guests with this Guest Tag. |
| `search` | string | no | Match by name, email or phone. |

Returns the rows of the Tracking page for one event, with each guest's status, how many are attending and their Guest Tags. Guest Tags show only if you are a host or co-host. Pass guest_id to get_guest or tag_guests.

Example response:

```json
{
  "guests": [
    {
      "guest_id": "g_20417",
      "name": "Maya Chen",
      "status": "attending",
      "total_attending": 2,
      "tags": []
    },
    {
      "guest_id": "g_20433",
      "name": "Jordan Reyes",
      "status": "opened",
      "total_attending": 0,
      "tags": []
    }
  ],
  "next_cursor": null
}
```

### get_guest

One guest: status, number attending and the messages sent to them. Access: read. REST: `POST /api/v1/paperless-post/get_guest`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Card or Flyer ID from list_events. |
| `guest_id` | string | yes | Guest ID from list_guests. |

Returns one row of the Tracking page with the broadcast and private messages sent to that guest. Use it to check what a guest already received before you write again.

Example response:

```json
{
  "guest_id": "g_20433",
  "name": "Jordan Reyes",
  "status": "opened",
  "total_attending": 0,
  "tags": [],
  "messages": [
    {
      "type": "broadcast",
      "subject": "Please RSVP by Friday",
      "sent_at": "2026-10-10T18:42:00-04:00"
    }
  ]
}
```

### export_guest_list

The Tracking page as a CSV download link, with each guest's RSVP status. Access: read. REST: `POST /api/v1/paperless-post/export_guest_list`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Card or Flyer ID from list_events. |

Returns a link to the CSV the Export guest list button on the Tracking page downloads. The link works for a limited time, so download it right away. Reads only; nothing changes in Paperless Post.

Example response:

```json
{
  "event_id": "ev_8F3K2Q",
  "rows": 41,
  "download_url": "https://files.cotlet.example/exports/ev_8F3K2Q-guests.csv"
}
```

### list_contacts

Your Address Book: names, emails and phone numbers saved for reuse. Access: read. REST: `POST /api/v1/paperless-post/list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Match by name, email or phone. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the contacts saved in your Address Book, so your agent can add known people to a guest list without a file. Matching by search is case insensitive.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": "c_7731",
      "name": "Maya Chen",
      "email": "maya@example.com"
    },
    {
      "contact_id": "c_7740",
      "name": "Jordan Reyes",
      "email": "jordan@example.com"
    }
  ],
  "next_cursor": null
}
```

### add_guests

Add guests to the unsent guest list of an event. Nothing is sent until send_invitation. Access: write. REST: `POST /api/v1/paperless-post/add_guests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Card or Flyer ID from list_events. |
| `guests` | object[] | yes | List of { name, email or phone, group_name, total_invited }. |

Adds guests to the unsent list, the same list the spreadsheet upload fills. Each guest needs a name and an email or phone number. Nothing reaches the guests until send_invitation, and you remove a guest in the app, so this call needs no confirmation.

Example response:

```json
{
  "event_id": "ev_8F3K2Q",
  "added": 2,
  "unsent_list_total": 2,
  "status": "unsent"
}
```

### send_invitation

Send the Card or Flyer to everyone on the unsent list, now or at a set time. Access: write, asks the user first. REST: `POST /api/v1/paperless-post/send_invitation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Card or Flyer ID from list_events. |
| `send_at` | datetime | no | ISO 8601 with time zone. Empty: send now. |

Sends the invitation to everyone on the unsent guest list. With send_at it is scheduled instead of sent now. Guests receive it as soon as it goes out. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "event_id": "ev_8F3K2Q",
  "status": "scheduled",
  "recipients": 41,
  "send_at": "2026-10-16T09:00:00-04:00"
}
```

### send_message

Broadcast from Messages & Reminders to guests by status and Guest Tag. Access: write, asks the user first. REST: `POST /api/v1/paperless-post/send_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Card or Flyer ID from list_events. |
| `template` | enum | no | reminder_to_rsvp, event_reminder, time_location_change or write_your_own. Default: write_your_own. |
| `message` | string | yes | Message text, up to 2,000 characters. No attachments. |
| `subject` | string | no | Email subject. |
| `statuses` | string[] | no | Guest statuses to reach, as shown on the Tracking page, for example attending. Default: all guests. |
| `tags` | string[] | no | Only guests with these Guest Tags. |

Sends a broadcast like the Messages & Reminders screen: pick a template or write your own, then recipients by guest status and optional Guest Tags. The text is limited to 2,000 characters and cannot carry attachments. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "event_id": "ev_8F3K2Q",
  "broadcast_id": "bc_51290",
  "status": "sent",
  "recipients": 23,
  "sent_at": "2026-10-10T18:42:00-04:00"
}
```

### send_private_message

Message one guest in their message log. Access: write, asks the user first. REST: `POST /api/v1/paperless-post/send_private_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Card or Flyer ID from list_events. |
| `guest_id` | string | yes | Guest ID from list_guests. |
| `message` | string | yes | Message text, up to 2,000 characters. |

Sends a private message to one guest, as the Private message option in Messages & Reminders does. The text is limited to 2,000 characters. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "event_id": "ev_8F3K2Q",
  "guest_id": "g_20433",
  "status": "sent",
  "sent_at": "2026-10-10T19:05:00-04:00"
}
```

### tag_guests

Add a Guest Tag to guests. Tags are visible to hosts and co-hosts only. Access: write. REST: `POST /api/v1/paperless-post/tag_guests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Card or Flyer ID from list_events. |
| `guest_ids` | string[] | yes | Guest IDs from list_guests. |
| `tag` | string | yes | Tag name; created if it does not exist. |

Adds one Guest Tag to the guests you list; the tag is created if it does not exist. Guest Tags need All Access pricing or Paperless Pro, otherwise the call fails. Tags reach no one and one call removes them, so this call needs no confirmation.

Example response:

```json
{
  "event_id": "ev_8F3K2Q",
  "tag": "lodging",
  "tagged": 2
}
```

## How do I connect Paperless Post to Claude Code, Codex or Cursor?

Connecting Paperless Post takes three steps: request access, sign in to Paperless Post once, then add one MCP server or call the REST API with the same key.

### Connect Paperless Post to your agent.

1. **Create an account** Sign up and add Paperless Post in the console. Your API key is there too.

2. **Sign in to Paperless Post once** Open the connect page from the console and sign in to Paperless Post the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Paperless Post tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Every Monday until the RSVP deadline, check the Summer Gala in Paperless Post, give me the headcount, and send a Reminder to RSVP to everyone who has not answered and was not reminded in the last 5 days. List anyone who bounced or unsubscribed so I can reach them myself.
```

### Call Paperless Post from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/paperless-post/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/paperless-post/send_message \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event_id":"ev_8F3K2Q","template":"reminder_to_rsvp","subject":"Please RSVP by Friday","message":"Hi! We are finalizing the headcount for the Summer Gala. Please reply by Friday.","statuses":["opened"]}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "event_id": "ev_8F3K2Q",
  "broadcast_id": "bc_51290",
  "status": "sent",
  "recipients": 23,
  "sent_at": "2026-10-10T18:42:00-04:00"
}
```

## Why use Cotlet for Paperless Post?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Paperless Post yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Paperless Post changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Paperless Post MCP server on GitHub?

No Paperless Post MCP server or Zapier app exists today. Hosts upload a guest spreadsheet per event, export RSVPs from the Tracking page and write each reminder in Messages & Reminders by hand; Cotlet gives your agent the same screens as tools.

|  | By hand | Cotlet |
|---|---|---|
| Setup | None, you click through the website | Request access, sign in to Paperless Post once, add one MCP server or API key |
| Guest lists | Fill the spreadsheet template and upload it per event | Your agent adds guests from any file or CRM export |
| RSVPs | Export the guest list as CSV and merge it yourself | Your agent reads statuses and answers live, or fetches the CSV link |
| When Paperless Post changes | You find the new button yourself | Our team tests it daily and fixes it for you; failed calls are free |
| Your session | Your browser; you log in again when it expires | Encrypted in an EU vault, revoked in one click; if Paperless Post logs you out, your agent gets a link to sign in again |
| Where it runs | Your browser, while you sit at it | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial with 5,000 credits, then credits per call |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Paperless Post changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Paperless Post API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Paperless Post API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Paperless Post account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Paperless Post yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Paperless Post tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Paperless Post in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Paperless Post's terms:** You use your own Paperless Post account and stay responsible for following Paperless Post's terms. Cotlet is independent and not affiliated with Paperless Post. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Request access and pick Paperless Post. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Paperless Post once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is a hosted server safe? My Paperless Post session would leave my computer.**

Cotlet keeps your Paperless Post session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Do Guest Tags work on every Paperless Post plan?**

No. Paperless Post offers Guest Tags with All Access pricing or a Paperless Pro subscription (checked 10 Oct 2026), and tags are visible to hosts and co-hosts only. On other plans tag_guests fails and the other tools still work.

**Can it attach a file to a reminder?**

No. Paperless Post does not allow attachments in follow up messages and caps messages at 2,000 characters, so send_message takes text only. Put a link to a shared file in the message instead.

**Can my agent post or send messages in Paperless Post without asking me?**

No. Every call to send_invitation, send_message or send_private_message waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_guests, tag_guests runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Paperless Post API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/paperless-post/{tool} from the HTTP Request node.