Connectors

Connectors let your agents use external services through Faramesh. Add them from the Integrations page. Every connector operation is governed by your policies, allow, deny, or require approval. All usage is logged in the audit.

All Connectors

Connector	Use Case	Key Operations
GitHub	Code and collaboration	get_repo, create_pr, merge_pr, issues
Stripe	Payments	refund, charge
AWS	Cloud infrastructure	EC2, S3, RDS, IAM
Jira	Project management	get_issue, create, update, transition, delete
Linear	Issue tracking	get_issue, create, update, delete, change_status
GCP	Google Cloud	VMs, storage buckets, service accounts
Azure	Microsoft Cloud	VMs, storage, blob
MongoDB	Database	create_collection, drop_collection, delete_many
Cassandra	Database	drop_keyspace, drop_table, truncate
Firebase	Backend services	write_realtime, delete, create/delete_document
Shopify	E-commerce	products, orders
WooCommerce	E-commerce	products, orders
X	Social media	post_tweet, delete_tweet, update_profile
Facebook	Social media	post, delete_post
Instagram	Social media	create_media, publish_media, delete_media

Adding a Connector

Go to Integrations in the dashboard
Connect your secrets manager (HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, or soon 1Password Business / Doppler)
Add connector credentials to your secrets manager at the paths in the Credential Broker guide
Faramesh fetches credentials ephemerally when policy allows an action, never stores them

Once connected, your agents can use it. Policies control which operations are allowed, denied, or need approval.

How It Works

When an agent uses a connector:

The operation is submitted to Faramesh
Your policy engine evaluates it (allow, deny, require approval)
If allowed → the connector runs and returns the result
If denied → the operation is blocked
If approval needed → you approve or deny from the dashboard, Slack, or email

All connector executions are stored in the audit log for compliance and forensics.

Table of content