Actions17
- Customer Actions
- Product Actions
- Service Actions
- Session Actions
Overview
This node integrates with the iBill.io API to perform operations on various resources such as Customer, Product, Service, and Session. Specifically, for the 'Service' resource with the 'Get' operation, it retrieves details of a service by its ID. It supports fetching the service either by an internal service ID or an external ID, based on the 'External' boolean flag. This node is useful for workflows that need to fetch service information from iBill.io, for example, to display service details, update records, or trigger other actions based on service data.
Use Case Examples
- Retrieve a service by its internal ID to update related customer records.
- Fetch a service using an external ID to synchronize data between systems.
Properties
| Name | Meaning |
|---|---|
| Service ID | The unique identifier of the service to retrieve. Required for the 'Get' operation on the 'Service' resource. |
| External | A boolean flag indicating whether to use the external ID (true) or the internal service ID (false) to fetch the service. |
Output
JSON
id- The unique identifier of the retrieved service.name- The name of the service.description- Description or details of the service.externalId- The external identifier of the service, if applicable.status- The current status of the service.
Dependencies
- Requires an API key credential for iBill.io API authentication.
Troubleshooting
- Common issues include invalid or missing service ID, resulting in errors from the API.
- If the 'External' flag is set incorrectly, the node may fail to find the service.
- Errors related to API authentication indicate issues with the provided API key credentials.
- The node throws an error if the operation returns undefined; ensure the API returns data or an empty array/object.
Links
- iBill.io API Documentation - Official API documentation for iBill.io, useful for understanding available endpoints and data structures.