Returns the chatHead (chat-message) of the pad in Etherpad

What this operation does

returns the chatHead (chat-message) of the pad

• POSTChanges data · padetherpad.local/getChatHead

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Etherpad operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Etherpad operations

• Returns the list of users that are currently editing this padPOST · changes data
• Creates a new (non-group) padPOST · changes data
• Creates a new groupPOST · changes data
• Creates a new authorPOST · changes data
• Creates a new sessionPOST · changes data
• Creates a new pad in this groupPOST · changes data
• Sends a custom message of type msg to the padPOST · changes data
• List all the padsPOST · changes data

All 96 Etherpad operations

Questions

Can HumDay returns the chathead (chat-message) of the pad in Etherpad?

Yes. This operation is published in Etherpad's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Etherpad data?

Yes — this is a POST operation, so it changes something in Etherpad. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Etherpad account.

Where this came from

Read from a published API description for Etherpad at pads.mro.name/api/openapi.json. The description above is the provider’s own wording, not ours. Last published 2021-01-07.