Tell Ably when a Coda document is deleted
Give downstream systems a clear signal to close or archive related work.
Trigger
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
Action
Publish Message to Channel
This tool will allow users to publish a message to a specified ably channel using a post request. it covers the essentials like channel name, message data, optional event name/type, and additional metadata for push notifications. it is an independent and fundamental operation within ably's real-time messaging platform.
Why this helps
Connected tools may keep acting on documents that no longer exist.
- Prevents stale downstream actions
- Creates a clear archive signal
- Improves workspace hygiene
Setup
Build it in a few focused steps.
- 1Connect Coda and Ably in the Notis portal once.
- 2Create an automation named document deletion broadcaster.
- 3Tell Notis to publish a deletion message with the returned document details to the chosen Ably channel.
- 4Pick Coda Document Deleted as the trigger.
- 5Choose where run reports go and test with one real deletion.
Questions about this workflow
Can downstream services archive their own records?
Yes. They can act on the deletion message received from Ably.
Can this recover a deleted document?
No. It only broadcasts the deletion event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Coda to Ably. A trigger fires from one place; an action lands in another.
Coda triggers
Ably actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Query Batch Presence
This tool enables querying the presence states of multiple channels in a single api request. the api retrieves the member presence details of the specified channels in parallel.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Query Batch Presence History
This tool enables querying presence history for multiple channels in a single api request. it uses the get endpoint at https://rest.ably.io/presence to retrieve the member presence history details of the specified channels in parallel.
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
Create Ably Channel
Creates a new channel or retrieves an existing channel in ably. this tool allows you to programmatically create and initialize channels for real-time messaging. since ably creates channels implicitly when first used, this action publishes an empty initialization message to create/activate the channel.
New Coda Document Trigger
Triggers when a new Coda document is created.
Delete Channel Subscription
This tool allows you to unsubscribe devices or clients from push notifications for specific channels. the operation is asynchronous, so immediate requests after deletion may briefly still return the subscription.
New Coda Page Trigger
Triggers when a new page is added to a Coda document.
Get Channel Details
This tool retrieves metadata and details for a specific channel in ably. it returns a channeldetails object containing information about the channel's status, occupancy, and other metadata. the endpoint provides visibility into channel activity, including metrics such as connections, presence, publishers, and subscribers, and requires appropriate permissions.
Specific Coda Page Updated Trigger
Triggers when a specific page within a Coda document is updated.
Get Channel History
This tool retrieves the message history for a specified ably channel. it uses the get /channels/{channelid}/messages endpoint to return a paginated list of messages in chronological order, subject to parameters such as 'channelid', 'limit', 'direction', 'start', and 'end'. the tool is useful for auditing, recovering missed messages, analyzing channel activity, and debugging message flows. authentication is required via basic or token authentication.
Get Channel Presence History
This tool retrieves the history of presence messages for a specified channel in ably. it allows you to query presence events on a channel within a given time period.
Get Ably Service Time
This tool retrieves the current server time from ably's service in milliseconds since the epoch. it is particularly useful for time synchronization and generating valid tokenrequest timestamps to prevent replay attacks. the endpoint supports multiple content types, handles http errors, network issues, and is a fundamental tool for ensuring accurate timing in ably applications.
Connect any two apps with Notis in the middle.
Coda and Ably, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Ably.