Synchronize timing for new Spotify devices
Anchor device events to Ably server time when timing consistency matters.
Trigger
New Device Added
Triggers when a new device is added.
Action
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.
Why this helps
Comparing timestamps from separate systems can make event ordering unclear.
- Consistent event timestamps
- Simpler cross system audits
- Clearer event ordering
Setup
Build it in a few focused steps.
- 1Connect Spotify and Ably in Notis.
- 2Create the automation.
- 3Describe that each new device event should retrieve Ably service time for the record.
- 4Select New Device Added as the trigger.
- 5Choose report delivery and test with one real event.
Questions about this workflow
What format is returned?
Ably service time is returned in milliseconds since the epoch.
Does this modify Spotify or Ably?
No, it retrieves the current Ably service time.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Spotify to Ably. A trigger fires from one place; an action lands in another.
Spotify 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.
New Device Added
Triggers when a new device is added.
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.
Spotify Playlist Item Change
Triggers when songs are added to or removed from a Spotify playlist.
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 Playlist Created or Deleted
Triggers when a new playlist is created or deleted.
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.
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.
Spotify 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.