Automations and Routines — Event-Driven and Scheduled Workflows

Overview Automations react when something happens in Evercore—uploads settle, shares open, export packs finish. Routines run on a schedule for retention sweeps, connector health checks, and recurring operational work. Both use the same graph executor, API scopes, and durable run history. Operators design flows in Console; production keys stay in tenant policy—not in a personal Zapier account. How it fits Evercore Workflows sit on the same trust layer as encrypted uploads, trace chainId timelines, and proof receipts. Trigger payloads match webhook event payloads and connector catalog names, so SIEM rules, ERP filters, and automation graphs agree on semantics. Runs emit automation.run. and routine.run. lifecycle events. steps_log and GET /automations/runs/live give operators a replayable record—useful for audits and connector fan-out without shadow scripts. Event automations vs routines Published automation graphs require config.actionId from GET /automations/catalog/actions. Routine schedules enforce a minimum interval (five minutes) and timezone-aware expressions. Trigger payload in graphs When an event fires, every node can reference the same data object documented under Webhook event payloads in the API reference: Toolkit nodes (GET /automations/catalog/node-types) cover transforms, flow.if, delays, Evercore API calls, and Composio integrations—roughly twenty node kinds today. Example: confirmation email after Arweave settlement A common regulated pattern: evidence uploads through Evercore, upload.completed delivers txId, fileName, and gateway url, and a published graph sends a Composio Gmail message to the matter lead with those fields in the body. Long-running runs can surface a token-gated cancel link from GET /automations/runs/control. Connect Gmail in Console (Agents → Connectors) before publish. Builder keys need automations:write; production keys should stay least-privilege. Schedule block for a weekly retention routine: Graphs that use schedules must include trigger.schedule; Evercore maintains next_run_at and last_run_at for operational visibility. Use cases on the platform • Event automation — Event-driven automation: react to catalog events without external cron. • Scheduled routines — Scheduled routines: clock-driven governance work on the same executor. • Agentic + connectors — Composio steps inherit connector policy from Console; combine with MCP-scoped agents when humans and agents share workflows. Explore next • Platform: /platform/automations and /platform/routines • API reference: Automations and Routines sections under /docs • Deeper scenario: Multi-backend governed flows when automation must respect ContentPolicy and anchors If Evercore is already your regulated storage layer, orchestration belongs inside that layer—not beside it with unaudited scripts.

Topics

• workflow automation
• event-driven automation
• scheduled routines
• Gmail confirmation email
• Composio integration
• system_action trigger