Connectors & Integrations

Connectors are outbound-only integrations — Atlas Studio initiates all connections to your infrastructure. No inbound ports, no agents listening on your servers.

Adding a Connector

Open Settings → Connectors → Add Connector
Select the connector type
Enter connection details
Click Test Connection — Atlas Studio verifies connectivity
Save

Connectors are stored locally in the Desktop IDE and optionally synced to the Web Portal Vault.

Supported Connectors

Observability

Kubernetes

Kubernetes


type: kubernetes
name: prod-cluster
kubeconfig: ~/.kube/config      # path or inline YAML
context: prod-eks               # optional: specific context
namespace: default              # optional: default namespace

Required permissions:


get, list, watch: pods, deployments, services, events, configmaps
exec: pods (for Coding Agent)

Datadog

Datadog


type: datadog
name: datadog-prod
apiKey: dd-api-key-xxxxxxxxxx
appKey: dd-app-key-xxxxxxxxxx
site: datadoghq.com             # or datadoghq.eu, us3.datadoghq.com

Prometheus

Prometheus


type: prometheus
name: prom-prod
url: https://prometheus.internal.company.com
# Optional basic auth:
username: prometheus
password: secret
# Optional: Bearer token
bearerToken: eyJ...

Elasticsearch

Elasticsearch


type: elasticsearch
name: elastic-logs
url: https://elasticsearch.internal.company.com:9200
username: atlas-reader
password: secret
# Or API key:
apiKey: base64encodedkey

CloudWatch

AWS CloudWatch


type: cloudwatch
name: aws-prod
region: us-east-1
# Uses default AWS credential chain (env vars, ~/.aws/credentials, IAM role)
# Or explicitly:
accessKeyId: AKIA...
secretAccessKey: secret

ITSM / Ticketing

ServiceNow


type: servicenow
name: snow-prod
instanceUrl: https://company.service-now.com
username: atlas-integration
password: secret
# Or OAuth:
clientId: xxx
clientSecret: xxx

PagerDuty


type: pagerduty
name: pagerduty-prod
apiKey: u+xxxxxxxxxxxx

OpsGenie


type: opsgenie
name: opsgenie-prod
apiKey: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
region: us               # or eu

Jira


type: jira
name: jira-prod
url: https://company.atlassian.net
email: atlas@company.com
apiToken: xxxxxxxxxxxxx  # Create at id.atlassian.com/manage-profile/security/api-tokens

Enterprise Systems

SAP

SAP (RFC, OData, IDoc)


type: sap
name: sap-prod
# For RFC:
host: sap-prod.company.com
systemNumber: "00"
client: "100"
username: ATLAS_USER
password: secret
language: EN
# For OData / REST:
baseUrl: https://sap-prod.company.com:4430
apiKey: xxx

SAP connectors require Pro or Enterprise plan. RFC connections require network access to the SAP application server port (default 3300).

Mainframe z/OS

Mainframe / z-OS


type: zos
name: mainframe-prod
zosmfUrl: https://mainframe.company.com:10443
username: ATLASID
password: secret
# For jobs requiring certificate auth:
certPath: /path/to/cert.pem
keyPath: /path/to/key.pem

IBM MQ

IBM MQ


type: ibmmq
name: mq-prod
restUrl: https://mq.company.com:9443
username: mqm
password: secret
queueManager: PROD.QM1

Kafka

Apache Kafka


type: kafka
name: kafka-prod
brokers:
  - kafka-1.company.com:9092
  - kafka-2.company.com:9092
# SASL_SSL:
saslMechanism: PLAIN
username: atlas
password: secret
ssl: true

Managing Connector Credentials

All connector credentials are stored in the OS keychain locally and optionally synced to the Web Portal Vault (AES-256-GCM encrypted).

Rotating credentials

Update the credential in your source system
In Atlas Studio: Settings → Connectors → select connector → Edit → update password/token
Click Test Connection to verify
Save — workflows using this connector will use the new credentials immediately (no restart required)

Settings → Connectors → select connector → Sync to Vault
The credential is encrypted and stored in the Web Portal
Team members can use this connector in their workflows without seeing the raw credentials

Testing Connectors

Always test a connector after creation or credential rotation:

Settings → Connectors → select connector → Test Connection
A green checkmark confirms connectivity
A red ✗ shows the error message — most common issues:
- Network timeout (check firewall rules)
- Authentication failed (wrong credentials)
- SSL certificate error (check TLS settings)

Connector Health Monitoring

Web Portal → Connectors → shows health status for all connectors:

Green: last test < 5 minutes ago, passed
Yellow: last test > 1 hour ago (stale)
Red: last test failed

Set up alerts: Web Portal → Connectors → Alert on Failure → Slack/email notification.