# Etherpad

> Write together in Etherpad from your workflows: make a pad for each meeting from a template, read its notes to archive or email them, add to it, post in its chat and find pads. Start a workflow when a pad is made, edited or gets a chat message.

App · 9 actions. Web page: https://docs.lodol.com/docs/integrations/etherpad

## Actions

### Copy pad

Copy a pad to a new one, such as a meeting template for each meeting, and get the new pad's link.

**Inputs**

- Pad (`pad`, text, required): The pad's name, or its link in Etherpad (such as https://pad.example.com/p/team-meeting); a read-only link works too.
- New name (`new_name`, text, required): The new pad's name: up to 50 characters, without / ? & # $ or :, such as team-meeting-2026-11-07.
- Copy history and chat (`with_history`, true/false): Copy the pad's history of changes and its chat too. Off, the copy starts fresh with only the text. Default: `false`.
- Replace it (`overwrite`, true/false): If a pad with the new name is already there, replace it. Off, the step stops instead. Default: `false`.
- Written as (`written_as`, text): The name Etherpad shows as the author of this change. Defaults to Lodol.

**Outputs**

- `copied_from` (text): The name of the pad it was copied from
- `id` (text): The pad's name, which other Etherpad steps take
- `last_edited` (text): When it was last changed (ISO 8601)
- `link` (text): Where the pad opens, to read and edit it
- `read_only_link` (text): A link that shows the pad without letting anyone edit it
- `revisions` (number): How many times it has been changed (its latest revision)

**Example output**

```json
{
  "copied_from": "meeting-template",
  "id": "team-meeting-2026-11-07",
  "last_edited": "2026-11-07T10:42:13Z",
  "link": "https://pad.example.com/p/team-meeting-2026-11-07",
  "read_only_link": "https://pad.example.com/p/r.c9ffa8107c86c659c3c5fdd6719194f5",
  "revisions": 1
}
```

### Create pad

Make a pad, such as the notes for a meeting, empty or with text or HTML to start from, and get its link to share.

**Inputs**

- Pad name (`pad`, text, required): The new pad's name, which is the end of its link: up to 50 characters, without / ? & # $ or :, such as team-meeting-2026-11-07.
- Content (`content`, text): What the pad starts with, such as an agenda. Leave blank for an empty pad.
- Format (`content_format`, text): Whether the content is plain text or HTML (with headings, bold, lists and links). Defaults to plain text. One of: `text` (Plain text), `html`. Default: `text`.
- If it exists (`if_exists`, text): What to do when a pad of that name is already there. Defaults to stopping with an error. One of: `error` (Stop with an error), `keep` (Use it as it is). Default: `error`.
- Written as (`written_as`, text): The name Etherpad shows as the author of this change. Defaults to Lodol.

**Outputs**

- `created` (true/false): Whether the pad was made now (false when it was already there)
- `id` (text): The pad's name, which other Etherpad steps take
- `last_edited` (text): When it was last changed (ISO 8601)
- `link` (text): Where the pad opens, to read and edit it
- `read_only_link` (text): A link that shows the pad without letting anyone edit it
- `revisions` (number): How many times it has been changed (its latest revision)

**Example output**

```json
{
  "created": true,
  "id": "team-meeting-2026-11-07",
  "last_edited": "2026-11-07T10:42:13Z",
  "link": "https://pad.example.com/p/team-meeting-2026-11-07",
  "read_only_link": "https://pad.example.com/p/r.c9ffa8107c86c659c3c5fdd6719194f5",
  "revisions": 1
}
```

### Delete pad

Delete a pad, with its history and chat. It can't be brought back.

**Inputs**

- Pad (`pad`, text, required): The pad's name, or its link in Etherpad (such as https://pad.example.com/p/team-meeting); a read-only link works too.

**Outputs**

- `deleted` (true/false): Whether the pad was deleted
- `id` (text): The deleted pad's name

**Example output**

```json
{
  "deleted": true,
  "id": "team-meeting-2026-11-07"
}
```

### Find pads

Find pads whose names contain some words or start with a prefix, A to Z or most recently edited first, with their links.

**Inputs**

- Name contains (`words`, text): Only pads whose names contain this, such as meeting.
- Name starts with (`starts_with`, text): Only pads whose names start with this, such as team-.
- Order (`sort`, text): Which come first. Sorting by last edit reads up to 500 pads. One of: `name` (By name, A to Z), `edited` (Most recently edited first). Default: `name`.
- How many (`limit`, number): The most to list. Defaults to 25. From 1 to 100.

**Outputs**

- `count` (number): How many are listed
- `has_more` (true/false): Whether more pads matched than were listed
- `pads` (list): The pads found
- `total` (number): How many pads matched in all

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "pads": [
    {
      "id": "team-meeting-2026-11-07",
      "last_edited": "2026-11-07T10:42:13Z",
      "link": "https://pad.example.com/p/team-meeting-2026-11-07"
    }
  ],
  "total": 1
}
```

### Get chat history

Get the latest messages in a pad's chat, oldest first, with who sent each and when.

**Inputs**

- Pad (`pad`, text, required): The pad's name, or its link in Etherpad (such as https://pad.example.com/p/team-meeting); a read-only link works too.
- How many (`limit`, number): The most recent messages to get. Defaults to 25, at most 500. From 1 to 500.

**Outputs**

- `count` (number): How many are listed
- `link` (text): Where the pad opens
- `messages` (list): The latest messages, oldest first
- `pad_id` (text): The pad's name
- `total` (number): How many messages the pad's chat has in all

**Example output**

```json
{
  "count": 1,
  "link": "https://pad.example.com/p/team-meeting-2026-11-07",
  "messages": [
    {
      "author_id": "a.KTgqpFEhdqHXOthl",
      "pad_id": "team-meeting-2026-11-07",
      "sender": "Lodol",
      "sent_at": "2026-11-07T10:45:00Z",
      "text": "Notes are ready for review."
    }
  ],
  "pad_id": "team-meeting-2026-11-07",
  "total": 1
}
```

### Get pad

Get what a pad says, as plain text and HTML, with who wrote in it, when it was last edited and its links, such as to archive it or email it after a meeting.

**Inputs**

- Pad (`pad`, text, required): The pad's name, or its link in Etherpad (such as https://pad.example.com/p/team-meeting); a read-only link works too.
- Revision (`revision`, number): Read the pad as it was at this revision (0 is when it was made). Leave blank for what it says now. At least 0.

**Outputs**

- `author_count` (number): How many people have written in it
- `authors` (list): Who has written in the pad
- `html` (text): What the pad says, as HTML with its formatting
- `id` (text): The pad's name, which other Etherpad steps take
- `last_edited` (text): When it was last changed (ISO 8601)
- `link` (text): Where the pad opens, to read and edit it
- `read_only_link` (text): A link that shows the pad without letting anyone edit it
- `revision_read` (number): Which revision the text and HTML are from
- `revisions` (number): How many times it has been changed (its latest revision)
- `text` (text): What the pad says, as plain text
- `users_online` (number): How many people have it open now

**Example output**

```json
{
  "author_count": 2,
  "authors": [
    {
      "id": "a.KTgqpFEhdqHXOthl",
      "name": "Lodol"
    },
    {
      "id": "a.8Ofh1Pv3XeYzQ2bd",
      "name": "Ada"
    }
  ],
  "html": "<!DOCTYPE HTML><html><body>Team meeting<br><br><ul class=\"bullet\"><li>Budget agreed</li><li>Next meeting on Friday</li></ul><br></body></html>",
  "id": "team-meeting-2026-11-07",
  "last_edited": "2026-11-07T10:42:13Z",
  "link": "https://pad.example.com/p/team-meeting-2026-11-07",
  "read_only_link": "https://pad.example.com/p/r.c9ffa8107c86c659c3c5fdd6719194f5",
  "revision_read": 12,
  "revisions": 12,
  "text": "Team meeting\n\n- Budget agreed\n- Next meeting on Friday\n",
  "users_online": 1
}
```

### Rename pad

Give a pad a new name, keeping its text, history and chat. Its link changes with it, and the old link no longer opens it.

**Inputs**

- Pad (`pad`, text, required): The pad's name, or its link in Etherpad (such as https://pad.example.com/p/team-meeting); a read-only link works too.
- New name (`new_name`, text, required): The new pad's name: up to 50 characters, without / ? & # $ or :, such as team-meeting-2026-11-07.
- Replace it (`overwrite`, true/false): If a pad with the new name is already there, replace it. Off, the step stops instead. Default: `false`.

**Outputs**

- `id` (text): The pad's name, which other Etherpad steps take
- `last_edited` (text): When it was last changed (ISO 8601)
- `link` (text): Where the pad opens, to read and edit it
- `old_id` (text): The pad's name before
- `read_only_link` (text): A link that shows the pad without letting anyone edit it
- `revisions` (number): How many times it has been changed (its latest revision)

**Example output**

```json
{
  "id": "team-meeting-2026-11-07",
  "last_edited": "2026-11-07T10:42:13Z",
  "link": "https://pad.example.com/p/team-meeting-2026-11-07",
  "old_id": "team-meeting",
  "read_only_link": "https://pad.example.com/p/r.c9ffa8107c86c659c3c5fdd6719194f5",
  "revisions": 12
}
```

### Send chat message

Post a message in a pad's chat, such as a reminder before a meeting or a note that the minutes were sent.

**Inputs**

- Pad (`pad`, text, required): The pad's name, or its link in Etherpad (such as https://pad.example.com/p/team-meeting); a read-only link works too.
- Message (`message`, text, required): What to say in the chat.
- Sent as (`sender`, text): The name the message shows as sent by. Defaults to Lodol.

**Outputs**

- `author_id` (text): The sender's author ID in Etherpad
- `link` (text): Where the pad opens
- `pad_id` (text): The name of the pad it's in
- `sender` (text): The name it was sent under; empty if they gave none
- `sent_at` (text): When it was sent (ISO 8601)
- `text` (text): What the message says

**Example output**

```json
{
  "author_id": "a.KTgqpFEhdqHXOthl",
  "link": "https://pad.example.com/p/team-meeting-2026-11-07",
  "pad_id": "team-meeting-2026-11-07",
  "sender": "Lodol",
  "sent_at": "2026-11-07T10:45:00Z",
  "text": "Notes are ready for review."
}
```

### Update pad

Replace what a pad says with new text or HTML, or add text to the end of it, such as a running log or the actions from a meeting.

**Inputs**

- Pad (`pad`, text, required): The pad's name, or its link in Etherpad (such as https://pad.example.com/p/team-meeting); a read-only link works too.
- Content (`content`, text, required): The new text, or the text to add to the end.
- Replace or add (`mode`, text): Whether the content replaces what the pad says, or is added to the end (plain text only). One of: `replace` (Replace the text), `append` (Add to the end). Default: `replace`.
- Format (`content_format`, text): Whether the content is plain text or HTML (with headings, bold, lists and links). Defaults to plain text. One of: `text` (Plain text), `html`. Default: `text`.
- Written as (`written_as`, text): The name Etherpad shows as the author of this change. Defaults to Lodol.

**Outputs**

- `id` (text): The pad's name, which other Etherpad steps take
- `last_edited` (text): When it was last changed (ISO 8601)
- `link` (text): Where the pad opens, to read and edit it
- `read_only_link` (text): A link that shows the pad without letting anyone edit it
- `revisions` (number): How many times it has been changed (its latest revision)

**Example output**

```json
{
  "id": "team-meeting-2026-11-07",
  "last_edited": "2026-11-07T10:42:13Z",
  "link": "https://pad.example.com/p/team-meeting-2026-11-07",
  "read_only_link": "https://pad.example.com/p/r.c9ffa8107c86c659c3c5fdd6719194f5",
  "revisions": 12
}
```
