Each organization object has a unique id. It also has a name, domain (the website of the organization), and persons associated with it.
The domain is an important attribute from an automation perspective, as it helps Affinity automatically link all the appropriate person objects to the organization.
Each organization also has a flag determining whether it's global or not.
As mentioned above, Affinity maintains its own database of global organizations that each customer has access to.
Note that you cannot change the name or the domain of a global organization.
You also cannot delete a global organization.
Of course, if an organization is manually created by your team, all fields can be modified and the organization can be deleted.
Dates of the most recent and upcoming interactions with an organization are available in the interaction_dates field.
This data is only included when passing {@link InteractionDatesQueryParams.with_interaction_dates}=true as a query parameter to the GET /organizations or the GET /organizations/{organization_id} endpoints.
Type declaration
Optionalperson_ids?: number[]
An array of unique identifiers of people (Person.id) that are associated with the organization.
Each organization object has a unique id. It also has a name, domain (the website of the organization), and persons associated with it. The domain is an important attribute from an automation perspective, as it helps Affinity automatically link all the appropriate person objects to the organization.
Each organization also has a flag determining whether it's global or not. As mentioned above, Affinity maintains its own database of global organizations that each customer has access to. Note that you cannot change the name or the domain of a global organization. You also cannot delete a global organization.
Of course, if an organization is manually created by your team, all fields can be modified and the organization can be deleted.
Dates of the most recent and upcoming interactions with an organization are available in the interaction_dates field. This data is only included when passing
{@link InteractionDatesQueryParams.with_interaction_dates}=true
as a query parameter to theGET /organizations
or theGET /organizations/{organization_id}
endpoints.