AtomicBI icon

AtomicBI

Interact with Atomic BI API
Join our community

Actions16

Overview

This node integrates with the Atomic BI API, allowing users to interact with various resources provided by the service. Specifically, for the "Playbooks" resource and the "Create" operation, it enables creating new playbook entries in Atomic BI. This is useful for automating the management of playbooks within data analytics or business intelligence workflows.

Typical use cases include:

  • Automating the creation of playbooks based on dynamic input data.
  • Integrating playbook creation into larger data processing pipelines.
  • Managing playbooks programmatically without manual intervention.

Properties

Name Meaning
Select List of fields to select from the playbook record. Leave empty to select all fields. Options include: Id, User Id, Space Id, Name, Instructions, Rules, Created At, Updated At, Mail, Chat, Browser, Linkedin, Objective, Bypass Agent

Output

The node outputs JSON objects representing the created playbook(s). Each output item contains a json field with the playbook data structured according to the selected fields. If multiple playbooks are created or returned, each will be an individual item in the output array.

No binary data output is indicated in the source code.

Dependencies

  • Requires an API key credential for authenticating with the Atomic BI API.
  • The node uses the Atomic BI API client internally, configured with the base URL and API key.
  • No additional external dependencies are required beyond the Atomic BI API access.

Troubleshooting

  • Invalid operation error: If an unsupported operation or resource is specified, the node throws an error indicating the invalid combination. Ensure that only supported operations (like "Create") and resources (like "Playbooks") are used.
  • Authentication failures: If the API key credential is missing or invalid, API calls will fail. Verify that the correct API key is configured in the node credentials.
  • Empty or incorrect field selection: Selecting no fields defaults to all fields, but specifying invalid field names may cause unexpected results. Use the provided list of selectable fields.
  • API errors: Network issues or API limits may cause failures. Check connectivity and API usage quotas.

Links and References

Discussion