Integrations

Integrations enable seamless interaction between the autobotAI platform and various third-party services, providing pre-built connections to streamline workflows and automate tasks. Through these integrations, you can connect to numerous external tools, enhancing the platform’s capabilities to suit diverse operational needs.

add_integrations

Available Integration Categories

Our platform supports a wide range of integrations across different categories:

  • Cloud Providers: AWS, Azure, Google Cloud Platform (GCP), and more.
  • AI Services: OpenAI, AWS Bedrock, and other AI platforms.
  • Communication & Notifications: Jira, AWS SES, Google Chat, Microsoft Teams, Slack, and more.
  • Agent-Based Systems: Kubernetes, Linux, and other environments.
  • Code Repositories: Git, GitHub, GitLab, and similar version control systems.
  • Monitoring Tools: Coralogix, Datadog, Email, Grafana, and more.
  • Security Tools: AbuseIPDB, Splunk, Cloudflare, GitGuardian, VirusTotal, and others.
list_integrations

Each integration provides specific functionalities that allow for seamless interaction with external tools and services.

Examples of Integration Use Cases

  • AWS Integration: Manage AWS resources such as creating, updating, and deleting EC2 instances or S3 buckets.
  • Microsoft Teams Integration: Send messages directly to Teams channels to enhance team communication within your automated workflows.

Additionally, users have the flexibility to create custom integrations using webhooks. This feature enables connections with unique services or applications that may not have pre-built connectors.

Secrets Management

autobotAI securely stores and manages secrets for integrations, databases, and APIs using AWS Secrets Manager.

Storing Secrets

  1. Navigate to the Integration > Secrets tab in the workspace console.
  2. Click “Add New Secret” and provide:
    • Name: Identifier for the secret
    • Value: Encrypted secret value (e.g., API keys, other secrets)
  3. Default secrets are stored in secured storage in customer's own data storage, alternatively customer can opt for AWS Secrets Manager as the storage provider as part of Enterprise support.

Rotating Secrets

  1. In autobotAI console, select your integration.
  2. Click “Configure” and follow prompts.
  3. Update integration config in autobotAI: Integration > Save
  4. Test integration connectivity.

Best Practices

  • Never hardcode credentials in workflow definitions or code.
  • Rotate secrets regularly based on compliance requirements:
    • Credentials: every 30–90 days
    • API keys: every 90 days
  • Use least-privilege IAM policies for secret access.
  • Monitor CloudTrail and Cloudwatch logs to review all API calls for audit.

Note:
Secrets are always encrypted at rest with customer-managed KMS keys.
For high-security environments, enable multi-region secret replication.