Actions24
- Computer Actions
- Maintenance Actions
- Person Actions
- Provider Link Actions
- Tag Actions
- Tenant Actions
- User Actions
Overview
The node named "ImmyBot" provides integration with the ImmyBot API, allowing users to interact with various resources and operations exposed by the service. Specifically, for the Provider Link resource and the Get Provider Link operation, the node retrieves detailed information about a specific provider link identified by its unique ID.
This node is beneficial in scenarios where automation workflows need to fetch configuration or status details of provider links managed within ImmyBot. For example, it can be used to verify the existence or properties of a provider link before proceeding with further automation steps, or to audit provider link data as part of a larger process.
Properties
| Name | Meaning |
|---|---|
| Provider Link ID | The unique identifier of the provider link to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the details of the requested provider link. The structure typically includes all relevant fields returned by the ImmyBot API for a provider link, such as its ID, configuration parameters, status, and metadata.
If the node supports binary data output (not indicated in the provided code), it would represent any file or media content associated with the provider link. However, based on the static analysis, the output is primarily JSON-formatted data.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials to access the ImmyBot API.
- The base URL for API requests is dynamically constructed using a subdomain value from the credentials.
- The node expects the environment to have network access to
https://<subdomain>.immy.bot/api/v1.
Troubleshooting
- Missing or invalid Provider Link ID: Ensure that the "Provider Link ID" property is correctly set and corresponds to an existing provider link in ImmyBot.
- Authentication errors: Verify that the OAuth2 credentials are properly configured and have not expired.
- Network issues: Confirm that the subdomain is correct and that there is internet connectivity to reach the ImmyBot API endpoint.
- API response errors: If the API returns errors, check the error message for details; common causes include insufficient permissions or incorrect resource identifiers.
Links and References
- ImmyBot API Documentation (Assumed URL for reference purposes)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/