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 supporting operations on various resources including "Account". The "Resend Checkpoint" operation for the Account resource allows users to trigger a resend of a checkpoint notification or verification related to a specific account. This can be useful in scenarios where an initial checkpoint message (such as a security verification or status update) was missed or not received by the user.
Practical examples include:
- Resending a verification checkpoint to an account when the user did not receive the original notification.
- Triggering a re-check or refresh of account status via the Unipile platform.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the account for which the checkpoint resend should be triggered. |
| Provider | The service provider associated with the account (e.g., email provider, social network). |
Output
The node outputs JSON data representing the response from the Unipile API after attempting to resend the checkpoint. This typically includes confirmation of the action or details about the updated checkpoint status. 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 payloads and expects JSON responses.
Troubleshooting
- Missing or invalid Account ID: Ensure the Account ID is provided and correctly formatted; otherwise, the API may reject the request.
- Invalid Provider value: The provider must match supported values recognized by the Unipile API.
- Authentication errors: Verify that the API key credential is valid and has necessary permissions.
- Network or API errors: Check connectivity and API availability; handle rate limits or server errors gracefully.
Common error messages might include authentication failures, invalid parameters, or resource not found errors. Resolving these usually involves verifying input properties and credential configurations.
Links and References
- Unipile API Documentation (general reference for API endpoints and usage)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes