Actions22
- App Actions
- Account Actions
- Channel Actions
- Message Actions
- Template Actions
- Contact Actions
- Tag Actions
- User Actions
- Team Actions
- Webhook Actions
Overview
This node integrates with the Poli API, providing a variety of operations across multiple resources such as apps, accounts, channels, messages, templates, contacts, tags, users, teams, and webhooks. Specifically, for the App resource with the Create App operation, it allows users to create a new application within their Poli account by specifying details like account ID, visibility, app name, description, responsible person, phone, email, and optionally a picture file ID.
Common scenarios where this node is beneficial include:
- Automating the creation of applications in Poli as part of a larger workflow.
- Managing multiple apps programmatically without manual intervention.
- Integrating app creation into CI/CD pipelines or onboarding processes.
Practical example:
- A marketing automation workflow that creates a new app in Poli whenever a new client signs up, populating all required fields automatically.
Properties
| Name | Meaning |
|---|---|
| Account ID | The identifier of the Poli account under which the app will be created. |
| Visibility | The visibility status of the app; options are Public or Private. |
| App Name | The name assigned to the new app. |
| Description | A textual description providing details about the app. |
| Responsible | The name or identifier of the person responsible for the app. |
| Phone | Contact phone number associated with the app or responsible person. |
| Contact email address associated with the app or responsible person. | |
| Picture File ID | (Optional) Identifier for an image file to associate as the app's picture or logo. |
Output
The node outputs JSON data representing the newly created app object returned from the Poli API. This typically includes the app's unique identifiers, metadata, and any other relevant information confirming successful creation.
If the node supports binary data output (not indicated explicitly here), it would relate to files such as the app's picture, but based on the provided code and properties, the output is primarily JSON.
Dependencies
- Requires an active connection to the Poli API via an API key credential configured in n8n.
- The node depends on the Poli API being accessible and the user having appropriate permissions to create apps.
- No additional external dependencies beyond the Poli API and its authentication.
Troubleshooting
- Error: Resource 'app' not found — Ensure the resource parameter is correctly set to "app".
- Error: Operation 'create' not found for resource 'app' — Verify the operation parameter is set to "create".
- API Authentication Errors — Confirm that the API key credential is valid and has sufficient permissions.
- Validation Errors — Required fields such as Account ID, App Name, Description, Responsible, Phone, and Email must be provided; missing these will cause errors.
- Network Issues — Check network connectivity to the Poli API endpoint.
- If the optional Picture File ID is invalid or points to a non-existent file, the API might reject the request.
Links and References
- Poli API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General API Authentication Best Practices
This summary is based solely on static analysis of the provided source code and property definitions.