Unipile icon

Unipile

Interact with Unipile API
Join our community

Actions85

Overview

The node interacts with the Unipile API to perform various operations on different resources. Specifically, for the Account resource and the Resync Account operation, it triggers a resynchronization process of an account's data within Unipile. This is useful when you want to refresh or update the local data cache with the latest information from the Unipile service.

Common scenarios include:

  • Ensuring that account data in your workflow is up-to-date after external changes.
  • Performing partial or full resynchronizations based on time spans or specific criteria.
  • Managing large datasets by chunking the synchronization process.

For example, you might use this node to resync a LinkedIn messaging account to fetch the latest messages or updates since the last sync.

Properties

Name Meaning
Account ID The unique identifier of the account to be resynchronized.
Additional Fields Optional parameters to customize the resync behavior:
- After Start of the time span (highest Epoch time in milliseconds) to limit the resync range.
- Before End of the time span (lowest Epoch time in milliseconds) to limit the resync range.
- Chunk Size Optional size of chunks to use during the resync process, useful for handling large data sets.
- Linkedin Product Specifies which LinkedIn messaging feature to synchronize.
- Partial Boolean flag indicating whether to perform a partial resync instead of a full one.

Output

The node outputs JSON data representing the result of the resynchronization request. This typically includes status information about the resync operation, such as success confirmation or details about the synchronized data.

If the node supports binary data output (not indicated here), it would represent any files or media fetched during the resync, but this is not evident from the provided code.

Dependencies

  • Requires an API key credential for authenticating with the Unipile API.
  • The base URL for API requests is configured via credentials (likely an environment-specific DSN).
  • No other external dependencies are indicated.

Troubleshooting

  • Missing or invalid Account ID: The node requires a valid Account ID; ensure this is provided and correctly formatted.
  • API authentication errors: Verify that the API key credential is set up properly and has sufficient permissions.
  • Invalid time span values: The after and before fields must be valid epoch timestamps; incorrect values may cause errors.
  • Chunk size issues: Setting an inappropriate chunk size (e.g., zero or negative) may lead to request failures.
  • Partial resync confusion: If partial resync is enabled but no relevant data exists, the operation might return empty results.

Common error messages will likely relate to HTTP status codes from the Unipile API, such as 401 Unauthorized (authentication issues), 400 Bad Request (invalid parameters), or 404 Not Found (account does not exist).

Links and References

Discussion