◆ INTEGRATIONS
Your agents react
to the world.
Connect to every tool your business already runs. Agents don't wait for you to start a conversation — they trigger on events: an email arrives, a Slack message is posted, a webhook fires, a schedule runs. The workforce shows up before you ask.
◆ HOW AGENTS ACTIVATE
Four ways an agent wakes up.
Agents aren't waiting in a chat box. They're subscribed to your systems, watching for the moment they're needed.
Webhook / Event
An event fires in your system — payment declined, chargeback opened, merchant onboarded — and the agent executes immediately. Zero latency from signal to action.
Inbound Message
Email or Slack message arrives — the agent reads it, classifies it, routes it, and acts on it before the human opens their inbox. The inbox becomes a trigger surface, not a queue.
Schedule
Cron-based triggers run agents on a cadence: daily reconciliation, weekly fee analysis, monthly compliance reports. Scheduled work happens without anyone scheduling it.
API Call
Trigger agents directly from your own product via REST API. Build AI-executed operations into your own workflows, dashboards, or automation pipelines with one API call.
POST /agents/execute with merchant context → agent runs onboarding playbook ◆ THE INTEGRATIONS
Every tool your business runs.
Pre-built connectors. Each one vaulted — agents never hold the API keys.
Productivity & Communication
Gmail
New email → agent reads, routes, acts
Google Calendar
Event scheduled → agent prepares context, sends briefs
Google Drive
File uploaded → agent processes, extracts, classifies
Outlook
Email received → agent triages and responds
Slack
Message in #ops-alerts → agent triages and routes
Microsoft Teams
Channel message → agent responds with action
Payment Infrastructure
Stripe
Chargeback opened → agent builds dispute case
PayPal
Dispute raised → agent tracks resolution workflow
Adyen
Transaction event → agent runs risk assessment
Braintree
Payment failed → agent logs, retries, notifies
Square
Refund requested → agent verifies and processes
CRM & Sales
Salesforce
Lead created → agent enriches and qualifies
HubSpot
Deal stage changed → agent updates tasks, notifies
Pipedrive
Activity due → agent prepares briefing, sends reminder
Project Management
Jira
Issue created → agent triages, assigns, estimates
Linear
Issue status changed → agent logs progress update
Asana
Task overdue → agent escalates and re-routes
Monday.com
Board item updated → agent syncs downstream systems
Notion
Database updated → agent creates task, sends summary
Data & Analytics
Google Sheets
Row added → agent processes and triggers workflow
Airtable
Record updated → agent runs enrichment pipeline
BigQuery
Query result ready → agent generates report, alerts
Snowflake
Pipeline complete → agent runs analysis, flags anomalies
◆ THE PARADIGM
The event-driven difference.
This is not a better chatbot. It's a different paradigm entirely.
e.g. Claude, ChatGPT
-
You initiate every interaction
You open a chat, type a question, get a response. Powerful — but you have to be there.
-
Advises and generates
Gives you the draft, the analysis, the recommendation. You still execute it.
-
Brilliant for ad-hoc reasoning
Complex questions, research, writing, analysis — ideal use case.
-
Waits for you
When you're not there, nothing happens. Chargebacks pile up. Emails sit unread.
shiftagent
-
Systems initiate the interaction
Webhook fires, email arrives, schedule triggers — agent activates before you even know it happened.
-
Executes the playbook
Doesn't draft the response — sends it. Doesn't suggest the task — creates and routes it. The work gets done.
-
Domain-specific and persistent
Knows your merchant's history, your processor relationships, your playbooks. Context accumulates over months.
-
Runs while you're away
Chargebacks handled at 2am. Reconciliation done before you arrive. Onboarding started the moment the webhook fires.
Conversational AI and event-driven agents aren't competing — they're complementary. Conversation is how you direct and review. Events are how work gets done autonomously between those conversations.
◆ CUSTOM INTEGRATIONS
If it has an API, your agent can use it.
Any REST endpoint, any webhook format, any authentication model — OAuth, API key, HMAC signature. Point the agent at it. The credential gets vaulted. The agent gets an alias. Your custom system becomes part of the workforce.
- Custom HTTP endpoints with any auth model
- Inbound webhooks in any JSON schema
- OAuth 2.0 flows with automatic token refresh
- HMAC signature validation on inbound events
- Custom headers, query params, request transforms
// POST /webhooks/events → agent execution triggered
{
"event": "chargeback.created",
"merchant_id": "mch_7f3c2a",
"amount": 284.50,
"reason_code": "4853",
"deadline": "2026-03-01T23:59:00Z"
}
// Agent response — automatic
{
"execution_id": "exe_9d1f...",
"playbook": "dispute_response_v3",
"status": "running",
"credential": "@stripe_live_key"
}Every integration credential is vaulted.
Agents never hold API keys for any integration — Stripe, Gmail, Salesforce, or your custom HTTP endpoint. Every credential is stored in the vault and represented to the agent as a scoped alias. The forward proxy resolves aliases at the network boundary only, only within the scope of an approved plan.
Learn about the vault architecture →Connect your stack in minutes.
Pre-built connectors for the tools you already run. Custom HTTP for everything else. Vaulted credentials from day one.