Restore key contact context after a device change
Resume outreach with the person record you need instead of rebuilding your context from scratch.
Trigger
New Device Added
Triggers when a new device is added.
Action
Get a single person
Use get `/v2/persons/fields` with `fieldids` or `fieldtypes` for detailed data; basic info by default. request multiple fields at once. "export all people" permission needed.
Why this helps
A device switch can interrupt outreach preparation and leave the next contact unclear.
- Bring one contact record into focus
- Reduce restart time after device changes
- Summarize permitted person fields clearly
Setup
Build it in a few focused steps.
- 1Connect Spotify and Affinity once in Notis.
- 2Create a new automation and name the person context lookup.
- 3Describe which Affinity person Notis should retrieve and how to summarize the contact context.
- 4Pick New Device Added as the trigger and choose a report channel.
- 5Test by adding one real Spotify device.
Questions about this workflow
Can this include custom person fields?
Yes, when permitted person field identifiers or field types are requested.
Can I include an outreach goal?
Yes. State the goal so Notis can organize the returned context around it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Spotify to Affinity. A trigger fires from one place; an action lands in another.
Spotify triggers
Affinity actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get a company s list entries
Summarize company data across all lists, including list-specific fields and metadata like creation date and author. access requires "export data from lists" permission.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get a company s lists
Returns metadata for all the lists on which the given company appears.
New Device Added
Triggers when a new device is added.
Get all companies
Affinity api allows paginated access to company info and custom fields. use `fieldids` or `fieldtypes` to specify data in a request. retrieve field ids/types via get `/v2/companies/fields`. export permission needed.
Spotify Playlist Item Change
Triggers when songs are added to or removed from a Spotify playlist.
Get all list entries on a list
Access and export essential data and metadata for companies, persons, or opportunities from a list, specifying data via `fieldids` or `fieldtypes`. "export data from lists" permission is necessary.
New Playlist Created or Deleted
Triggers when a new playlist is created or deleted.
Get all list entries on a saved view
Use the endpoint to access rows in a saved view with specific filters and selected fields from a web app. it doesn't maintain sort order, supports only sheet-type views, and requires export permissions.
Get all opportunities
Pagination through opportunities in affinity yields basic info but excludes field data. for field data, use specified get endpoints. "export data from lists" permission needed.
Get all persons
The affinity api offers paginated access to person data using `fieldids` or `fieldtypes`. bulk extraction needs special permissions and supports multiple parameters.
Get a person s list entries
Summary: browse rows for a person in all lists, showing field data and entry metadata like creation time and author. requires "export data from lists" permission.
Connect any two apps with Notis in the middle.
Spotify and Affinity, 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 Affinity.