Actions113
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Contacts API Actions
- Inbox API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Custom Attributes Actions
- Canned Response Actions
Overview
This node operation retrieves detailed information about all integrations associated with a specific account. It is useful when you need to list or audit all the integrations configured for an account in a system that supports such integrations. For example, a user might want to fetch all third-party services connected to their account to monitor or manage them.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account to query. |
Output
The output will be a JSON object containing details of all integrations linked to the specified account. Each integration's data typically includes identifiers, configuration details, status, and other metadata relevant to the integration. The exact structure depends on the API response but generally provides comprehensive information about each integration.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential to authenticate requests.
- The node interacts with an external API endpoint (base URL provided via credentials).
- Proper configuration of the API URL and authentication token is necessary in the node credentials.
Troubleshooting
Common issues:
- Invalid or missing account ID: Ensure the "Account Id" property is set correctly as a number.
- Authentication failures: Verify that the API key or authentication token is valid and has sufficient permissions.
- Network errors: Check connectivity to the API endpoint and ensure no firewall or proxy blocks the request.
Error messages:
- Unauthorized or 401 errors indicate invalid credentials.
- 404 errors may mean the account ID does not exist or is inaccessible.
- Timeout or network errors suggest connectivity problems.
Resolving these usually involves verifying input parameters, credentials, and network settings.
Links and References
- Refer to the API documentation of the service managing integrations for detailed schema and examples.
- Consult n8n documentation on setting up API credentials and handling HTTP request nodes for more context on authentication and error handling.