AI workflows for customer support & AI automation for tickets and CRM
Automate customer support with AI: listen on the systems you already connected, call the same assistant customers see on the web, then write back to Slack, Teams, CRMs, inboxes, or HTTP endpoints. Build AI agents for business workflows with AI customer engagement automation—sample flows below; the live catalog matches connector pickers in the product.
Apps that power triggers & actions (36)
Logos use the proxied brand endpoint for accurate color; third-party marks belong to their owners.
- Each automation starts with a catalog trigger (event, schedule, or webhook), then one or more actions—including “call this agent” and outbound posts to connected apps
- Connections are per agent inside Automations; the same OAuth and API key flows you use for knowledge apply here
- Built-in FlexyAgents steps cover incoming webhooks, agent inference, and outbound HTTP so you are not blocked when a vendor is custom
- Plans cap active automations and monthly runs; webhook-style triggers can be feature-gated until you upgrade
Open an agent, go to Automations, then add connections before you publish a flow.
Samples
Visual recipes you can recreate
Each strip is illustrative—exact trigger and action names come from your live catalog once apps are connected. The agent icon represents the same FlexyAgents assistant you configure for chat.
Support ticket → agent → Slack
When Zendesk creates or updates a ticket, run the agent on the thread, then notify #support with a summary link.
ZendeskFlexyAgents agentSlackNew Shopify order → agent → Teams
Commerce signal fires on a new order; the agent drafts a short recap and Microsoft Teams gets the ping for fulfillment.
ShopifyFlexyAgents agentMicrosoft TeamsInbound webhook → agent → HubSpot
POST payloads hit your FlexyAgents webhook URL, the agent interprets the body, and CRM fields update via HubSpot actions.
WebhookInbound webhookFlexyAgents agentHubSpotHubSpot contact change → agent → email
CRM creates or updates a contact; the agent summarizes next-best action and SendGrid sends the follow-up.
HubSpotFlexyAgents agentSendGridCalendar event → agent → Slack
Google Calendar creates or updates an event; the agent formats a briefing and posts to the right channel.
Google CalendarFlexyAgents agentSlackNotion page change → agent → Discord
Docs shift in Notion; the agent summarizes deltas for moderators on Discord.
NotionFlexyAgents agentDiscord
In the product
Triggers, steps, and the agent in the middle
Authoring mirrors what you see after sign-in: pick an app trigger, stack actions, map fields, and save. Execution logs surface success, retries, and provider errors.
Event-first triggers
Slack mentions, Zendesk tickets, Shopify orders, calendar changes, and dozens of other catalog entries can open a run—exact slugs depend on what your workspace connected.
- Webhook triggers expose a signed URL under /api/webhooks/automations/…
- Polling and vendor push events both end in the same executor pipeline
- Trigger payloads flow into step input mapping with optional transforms
Agent steps are first-class
Any automation can call the same agent you expose on the web widget—ideal for summarization, classification, or drafting replies before another action posts them.
- Reuse prompts, tools, and knowledge bases without duplicating configuration
- Chain multiple agent calls when you need review then rewrite
- Responses become variables for the next HTTP or chat action
Multi-step graphs
After the trigger, add CRM updates, Slack messages, email sends, or raw REST calls. Conditions and error branches keep noisy vendors from wedging the whole run.
- Ordering is explicit—no hidden DAG unless you build it that way
- Failed steps can short-circuit or fall back per automation settings
- Great for “notify + update record + log to analytics” patterns
Describe-to-draft helper
The add-automation modal can propose a JSON-shaped flow from natural language when your org already connected the relevant apps.
- Examples ship per app—Zendesk→Slack, Notion updates, Shopify orders, and more
- You still review before save; nothing runs until you publish
- Helpful when PMs prototype before engineers touch low-level mapping
Credentials
Same connection manager as knowledge and channels
OAuth apps redirect through the standard consent screens; API key apps collect structured fields (Twilio SID, Zendesk subdomain, etc.). Disconnected apps simply do not appear in trigger pickers.
OAuth for the household names
Slack, Microsoft, Google, Atlassian, Shopify, Salesforce, and Meta flows reuse the tokens you already trust for messaging deployments.
- Tokens stay scoped to the agent that created the connection
- Reconnect from Automations without deleting historical runs
- Matches the modal copy in AppConnectionManager
API keys where vendors require them
Telegram bots, WhatsApp Business, Twilio, SendGrid, Zendesk API tokens, and similar patterns collect the extra fields those vendors demand.
- Keys encrypt at rest like LLM provider secrets
- Rotate from the same dialog without unpublishing automations
- Clear error toasts when a key expired mid-run
Catalog categories
Browse triggers by Messaging, Knowledge base, CRM, E-commerce, Storage, or Calendar—the same taxonomy the dashboard uses today.
- Helps CS, revops, and IT each find their surfaces quickly
- Inactive vendor apps never clutter the picker
- New integrations land in the database catalog without redeploying marketing
Plans
Automation slots, monthly runs, webhook gates
Free defaults include a small number of active automations and monthly runs, with webhook triggers opt-in on higher tiers—check pricing for your exact row.
Usage meters
Organizations track how many automations are defined and how many runs executed in the billing month—overage behavior follows your subscription.
- Run counter increments after successful executor handoffs
- Admins see totals next to other plan limits
- Add-ons can bump automation runs when sold that way
Webhook triggers
Some plans keep webhook triggers off until you upgrade, so only vendor-native events fire first—this prevents surprise traffic on entry SKUs.
- FlexyAgents-native webhook URLs still document clearly in settings
- Upgrade unlocks custom ingress from your own services
- Pairs with the HTTP actions for round-trip integrations
Deploy assistants everywhere on Channels, sync context from Connectors, and read model billing on Hosted vs BYOK.
Next step
Connect apps, then automate the busywork
Wire credentials once per agent, drop in a trigger, stack actions, and let the assistant handle summarization or drafting before anything posts to your team.