Keep Affinity person fields easy to use
Give every research prompt a clear view of the person data available.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get metadata on person fields
Returns metadata on non-list-specific person fields. use the returned field ids to request field data from the get `/v2/persons` and get `/v2/persons/{id}` endpoints.
Why this helps
Teams ask vague questions when they cannot see which person fields exist.
- Write clearer lookup prompts
- Improve onboarding research
- Reduce repeated field discovery
Setup
Build it in a few focused steps.
- 1Connect Zendesk and Affinity once in Notis.
- 2Create an automation describing the person-field reference to produce.
- 3Pick a recurring schedule as the trigger.
- 4Choose where reports go and test with one run.
Questions about this workflow
Does this retrieve individual people?
No. It returns metadata about non-list-specific person fields.
Can support use this with tickets?
Yes. Use the catalog to request relevant person fields in a ticket workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Affinity. A trigger fires from one place; an action lands in another.
Zendesk 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 User Created
Triggered when a new user is created in Zendesk.
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.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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.
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.
Zendesk 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.