Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
The node provides integration with a universal messaging gateway platform, allowing users to manage and interact with various messaging platforms within projects. Specifically, the "Platforms" resource with the "List" operation enables users to retrieve a list of all configured messaging platform integrations for a specified project.
This functionality is beneficial in scenarios where you want to programmatically access and manage the platforms connected to your messaging gateway project, such as auditing available platforms, synchronizing platform configurations, or dynamically displaying platform options in workflows.
Example use cases:
- Listing all messaging platforms integrated into a project to display them in a dashboard.
- Automating checks on platform configurations before sending messages.
- Synchronizing platform data with other systems or services.
Properties
| Name | Meaning |
|---|---|
| Project | Project identifier to operate on (string). This specifies which project's platforms to list. |
Output
The output will be a JSON array containing the list of platform configurations associated with the specified project. Each item in the array represents a platform integration with its details such as platform type, name, description, credentials (likely masked or omitted), status, and other metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authentication to the messaging gateway API.
- The node makes HTTP GET requests to the endpoint
/api/v1/projects/{project}/platformsto fetch the list. - The user must configure the node with valid credentials and specify the correct project identifier.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect project identifier may result in empty results or errors indicating the project does not exist.
- Network connectivity issues can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid or expired API keys; ensure the API key credential is correctly set up.
- "Project not found" errors suggest the provided project ID does not exist or the user lacks permission.
- Timeout or connection errors require checking network access and API availability.
Links and References
- Refer to the messaging gateway API documentation for detailed information about platform management endpoints.
- Consult n8n documentation on how to configure API key credentials and use HTTP request nodes if needed.