Actions85
- Account Actions
- Calendar Actions
- Email Actions
- LinkedIn Actions
- Close Job Posting
- Create Job Posting
- Download Applicant Resume
- Edit Job Posting
- Endorse Skill
- Get Company Profile
- Get Hiring Project by ID
- Get Hiring Projects
- Get Inmail Balance
- Get Job Applicant
- Get Job Applicants
- Get Job Offer
- Get Job Postings
- Get Raw Data
- Perform Action on Member
- Publish Job Posting
- Search
- Search Parameters
- Solve Job Publishing Checkpoint
- Messaging Actions
- Post Actions
- User Actions
- Webhook Actions
Overview
This node allows sending messages in a chat via the Unipile API. It is designed to interact with the messaging resource of Unipile, specifically to send chat messages programmatically. This can be useful for automating communication workflows, such as sending notifications, alerts, or updates directly into chat channels without manual intervention.
Practical examples include:
- Automatically sending a message to a team chat when a new task is created.
- Posting alerts from monitoring systems into a chat group.
- Sending reminders or status updates to a chat channel based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the chat where the message will be sent. |
| Body (JSON) | The raw JSON payload representing the message content and any additional parameters required by the API to send the message. |
Output
The node outputs JSON data representing the response from the Unipile API after attempting to send the message. This typically includes confirmation details such as message ID, status, timestamps, or error information if the operation failed.
If the API supports binary data in responses (e.g., attachments), the node would handle it accordingly, but based on the provided code and properties, the primary output is JSON structured data related to the sent message.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for the API is configured via credentials (referred to generically as an API endpoint URL).
- The node expects the Unipile API to accept and return JSON-formatted data.
Troubleshooting
- Missing or invalid Chat ID: Ensure the Chat ID is correctly specified and corresponds to an existing chat in Unipile.
- Malformed JSON in Body: The Body property must contain valid JSON. Invalid JSON will cause request failures.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- API endpoint issues: Confirm that the base URL configured in credentials is correct and accessible.
- Error responses from API: Check the returned JSON for error messages indicating issues like rate limits, permission denials, or invalid parameters.
Links and References
- Unipile API Documentation (generic placeholder link)
- n8n documentation on Creating Custom Nodes