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 interacts with the Unipile API to list invitations sent by a user account. It is useful for scenarios where you need to retrieve and manage the invitations that have been sent from a specific user account, such as monitoring outreach efforts or auditing invitation statuses.
A practical example would be fetching all invitations sent from a particular account to display them in a dashboard or to process them further in an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the user account whose sent invitations you want to list. |
| Additional Fields | Optional parameters to refine the query: |
| - Cursor | A pagination cursor to fetch the next set of results. |
| - Limit | Maximum number of invitations to return (minimum 1, default 50). |
Output
The node outputs a JSON array containing the list of invitations sent by the specified user account. Each item in the array represents an invitation with its associated details as returned by the Unipile API.
If the API supports it, the output may include pagination information to allow fetching subsequent pages using the cursor.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for the API is configured via credentials.
- Proper network access to the Unipile API endpoint is necessary.
Troubleshooting
- Missing or invalid Account ID: Ensure the Account ID property is provided and correctly formatted; otherwise, the API call will fail.
- API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Pagination issues: If using the cursor for pagination, ensure it is correctly passed; otherwise, you might receive repeated or incomplete results.
- Rate limiting or API errors: Handle HTTP errors gracefully and consider implementing retries or backoff strategies if supported.
Links and References
- Unipile API Documentation (example link, replace with actual)
- n8n documentation on HTTP Request Node for understanding API integrations