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
The node interacts with the Unipile API, specifically handling user-related operations. The "Handle Invitation Received" operation allows users to process an invitation by providing its unique ID and a JSON body containing relevant data. This is useful in scenarios where an application needs to programmatically accept, decline, or otherwise manage invitations received through the Unipile platform.
Practical examples include:
- Automatically accepting meeting invitations sent via Unipile.
- Processing collaboration requests or group join invitations.
- Managing event or calendar invites within automated workflows.
Properties
| Name | Meaning |
|---|---|
| Invitation ID | The unique identifier of the invitation to be handled. |
| Body (JSON) | A raw JSON object containing the data required to handle the invitation (e.g., response). |
Output
The node outputs a JSON object representing the result of handling the invitation. This typically includes confirmation details such as status updates, any messages returned by the API, or updated invitation information. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for API requests is configured from the credential's DSN property.
- The node sends HTTP requests with JSON content type headers.
Troubleshooting
- Invalid Invitation ID: If the provided invitation ID does not exist or is malformed, the API may return an error. Verify the ID before running the node.
- Malformed JSON Body: Ensure the JSON body is correctly formatted; invalid JSON will cause request failures.
- Authentication Errors: Missing or incorrect API credentials will prevent successful API calls. Confirm that the API key credential is properly set up.
- Network Issues: Connectivity problems can cause timeouts or failed requests. Check network access to the Unipile API endpoint.
Links and References
- Unipile API Documentation (hypothetical link for reference)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics