Actions82
- Account Actions
- Account Audit Actions
- Billing Entry Actions
- Call Detail Record Actions
- Carrier Actions
- Device Actions
- Device Template Actions
- Email Template Actions
- Feature Code Actions
- File Actions
- Flow Actions
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
Overview
This node interacts with the TeleFlow API to perform various operations on different resources, including Carriers. Specifically, the "Get" operation for the Carrier resource retrieves detailed information about a single carrier by its unique ID. This is useful when you need to fetch specific carrier details such as configuration or status within your workflow.
Practical examples:
- Fetching carrier details before updating or deleting it.
- Retrieving carrier information to display or use in conditional logic.
- Integrating carrier data into reports or dashboards.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the carrier resource to retrieve. This is required. |
| Fields | Optional key-value pairs specifying additional fields to include in the request query string. You can add multiple field name and value pairs to filter or customize the returned data. |
Output
The output is a JSON object representing the carrier resource retrieved from the TeleFlow API. It contains all the properties of the carrier as returned by the API, potentially filtered or customized based on the optional fields provided.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"id": "carrier-id",
"name": "Carrier Name",
"status": "active",
"otherProperties": "..."
}
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication credential configured in n8n (an API key or token).
- The base URL for the API must be set in the node credentials.
Troubleshooting
- Missing ID error: If the ID property is not provided, the node will throw an error stating that the ID is required for the get operation. Ensure you provide a valid carrier ID.
- API connection issues: Errors related to network connectivity or invalid credentials may occur. Verify your API key/token and base URL are correct.
- Invalid fields: Providing incorrect field names in the Fields property might result in unexpected API responses or errors. Double-check field names against the TeleFlow API documentation.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/