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 providing functionality to reconnect an existing account. This operation is useful when an account's connection has expired or been disrupted and needs to be re-established without creating a new account from scratch. For example, if an integration token has expired or permissions have changed, this node can send updated connection details to restore access.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the account to reconnect. This is required to specify which account to update. |
| Body (JSON) | A raw JSON object containing any additional data needed to reconnect the account. This allows sending custom parameters as required by the API during reconnection. |
Output
The node outputs JSON data representing the response from the Unipile API after attempting to reconnect the specified account. This typically includes confirmation of the reconnection status, updated account details, or error information if the operation failed. 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 via credentials.
- The node sends HTTP requests with JSON content type headers.
Troubleshooting
- Invalid Account ID: If the provided Account ID does not exist or is incorrect, the API will likely return an error indicating the account was not found. Verify the Account ID before retrying.
- Malformed JSON Body: Providing invalid JSON in the "Body (JSON)" property may cause request failures. Ensure the JSON syntax is correct.
- Authentication Errors: Missing or invalid API credentials will prevent successful reconnection. Confirm that the API key credential is correctly set up.
- API Endpoint Issues: Network problems or incorrect base URL configuration can cause request failures. Check connectivity and credential settings.
Links and References
- Unipile API Documentation (example placeholder link)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes