◆ 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
Agents read, triage, route, and respond to inbound messages — then file documents, update calendars, and prepare briefings without being asked.
Gmail
Google Calendar
Google Drive
Outlook
Slack
Microsoft Teams
Payment Infrastructure
Agents monitor transactions, handle chargebacks and disputes, process refunds, run risk assessments, and reconcile settlements across your payment stack.
Stripe
PayPal
Adyen
Braintree
Square
Accounting
Agents reconcile bank feeds, match invoices to payments, categorize expenses, generate financial reports, and manage accounts receivable across your books.
QuickBooks
Xero
Sage
Zoho Books
FreshBooks
NetSuite
CRM & Sales
Agents enrich and qualify leads, update deal stages, prepare meeting briefings, and keep your pipeline in sync across every system.
Salesforce
HubSpot
Pipedrive
Zoho CRM
Freshsales
Project Management
Agents triage issues, assign work, track progress, escalate blockers, and keep downstream systems in sync as tasks move through your pipeline.
Jira
Linear
Asana
Monday.com
Notion
Data & Analytics
Agents process new data as it arrives, run enrichment pipelines, generate reports, and flag anomalies across your analytics stack.
Google Sheets
Airtable
BigQuery
Snowflake
◆ 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.