TeleFlow icon

TeleFlow

Interact with TeleFlow API
Join our community

Actions145

Overview

This node interacts with the TeleFlow API to perform various operations on different resources, including Tenant Audit. Specifically, for the "Tenant Audit" resource and the "Create" operation, the node sends a POST request to create a new tenant audit record in the TeleFlow system.

Common scenarios where this node is beneficial include automating the creation of audit records related to tenants within a telecommunication or VoIP management platform. For example, when a new tenant is added or modified, an audit entry can be created automatically to track changes or events for compliance and monitoring purposes.

Properties

Name Meaning
Fields A collection of field-value pairs to include in the request. You can add multiple fields, each specifying a field name and its corresponding value to customize the data sent in the create request.

The "Fields" property allows users to specify arbitrary key-value pairs that will be included in the request body, enabling flexible and specific data submission for creating a tenant audit record.

Output

The node outputs JSON data representing the response from the TeleFlow API after creating the tenant audit record. This typically includes details of the newly created audit entry such as its ID, timestamps, and any other metadata returned by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the TeleFlow API.
  • The base URL for the TeleFlow API must be configured in the node credentials.
  • The node uses HTTP requests to communicate with the TeleFlow API endpoints.

Troubleshooting

  • Missing Required Fields: If required fields are not provided in the "Fields" collection, the API may reject the request. Ensure all mandatory data is included.
  • Authentication Errors: If the API key or base URL is incorrect or missing, authentication will fail. Verify the credential configuration.
  • API Endpoint Issues: The node constructs the endpoint URL based on the resource name pluralized (e.g., /tenantAudits). If the resource name or operation is incorrect, the request may fail.
  • Error Handling: If an error occurs during execution, it is logged, and if "Continue On Fail" is enabled, the error message is returned in the output JSON under an error key.

Links and References

Discussion