Actions16
Overview
This node interacts with the Outseta CRM API to retrieve multiple account records based on specified filters and options. It is useful for scenarios where you need to fetch a list of accounts from your CRM system, optionally filtered by criteria such as account name, stage, or associated person details. For example, you might use this node to generate reports on accounts in a specific sales stage or to synchronize account data with another system.
Properties
| Name | Meaning |
|---|---|
| Additional Options | A collection of optional filters and parameters to refine the query when retrieving accounts: |
| - Fields | Comma-separated list of fields to return (e.g., Uid, Email, FirstName, LastName) |
| - Filter by Account Name | Filter accounts by their exact name (e.g., "Acme Corp") |
| - Filter by Account Stage | Filter accounts by their stage; options include Demo, Trialing, Subscribing, Cancelling, Expired, Trial Expired, Past Due |
| - Filter by Person Email | Filter accounts by an associated person's email address |
| - Filter by Person UID | Filter accounts by an associated person's unique identifier |
| - Limit | Maximum number of results to return (minimum 1, default 50) |
| - Offset | Number of results to skip before starting to return results (minimum 0, default 0) |
Output
The node outputs an array of JSON objects representing the accounts retrieved from the Outseta CRM. Each object contains the fields requested via the Fields property or all available fields if none are specified. The output does not include binary data.
Example output structure (fields depend on request):
[
{
"Uid": "account-uid-123",
"Name": "Acme Corp",
"Email": "[email protected]",
"AccountStage": 3,
...
},
...
]
Dependencies
- Requires an API key credential for authenticating with the Outseta CRM API.
- The node expects the domain of the Outseta instance to be configured in credentials.
- Network access to the Outseta API endpoint (
https://{domain}/api/v1) is required.
Troubleshooting
- No results returned: Check that filter values match existing data exactly (e.g., account names are case-sensitive).
- Invalid field names in
Fields: Ensure the comma-separated list uses valid field names recognized by the Outseta API. - Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Rate limiting or API errors: If the API returns errors, check the Outseta API status and consider adding error handling or retries in your workflow.