Actions16
Overview
This node integrates with the Outseta CRM API to retrieve detailed information about a specific person stored in the CRM system. By providing the unique identifier (UID) of a person, it fetches that person's data from Outseta.
Common scenarios where this node is useful:
- When you need to enrich workflow data with detailed contact information from your CRM.
- To verify or display person details before performing further actions like updates or notifications.
- To automate processes that depend on retrieving up-to-date person records by their UID.
Practical example:
You have a workflow triggered by a form submission containing a person's UID. This node fetches the full profile of that person from Outseta, allowing subsequent nodes to use their email, name, or other attributes for personalized emails or reporting.
Properties
| Name | Meaning |
|---|---|
| Person UID | The unique identifier of the person to retrieve from the Outseta CRM. This is required. |
Output
The node outputs JSON data representing the person object retrieved from the Outseta CRM. This JSON includes all available fields for the person as returned by the API, such as email, first name, last name, phone numbers, timezone, and any custom fields configured in Outseta.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Outseta CRM API.
- The node expects the Outseta domain to be configured in credentials to construct the base URL for API requests.
- Network access to the Outseta API endpoint (
https://<your-domain>/api/v1) must be available.
Troubleshooting
- Missing or invalid Person UID: If the
Person UIDproperty is empty or incorrect, the API will return an error indicating the resource was not found. Ensure the UID is correct and corresponds to an existing person. - Authentication errors: If the API key credential is missing, invalid, or expired, the node will fail with authentication errors. Verify the API key and domain configuration.
- Network issues: Timeouts or connectivity problems can cause failures. Check network access and proxy settings if applicable.
- API rate limits: Excessive requests may be throttled by Outseta. Implement retry logic or reduce request frequency if needed.
Links and References
- Outseta API Documentation — Official API reference for understanding person objects and endpoints.
- Outseta CRM — Learn more about the CRM platform integrated by this node.