Read Front's automation Rules configuration via the read-only Rules API
domain: dev.frontapp.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request the rules:read scope for your Front API token or app
List all company-level (org-wide) rules with GET https://api2.frontapp.com/company/rules
List rules scoped to one teammate with GET https://api2.frontapp.com/teammates/{teammate_id}/rules (teammate_id accepts a resource alias like an email address)
Inspect each returned rule's human-readable conditions/actions to understand what automation already exists before building on top of it
To react to rule executions rather than just inspect definitions, subscribe to Front's Rule webhooks or use application triggers, since rule authoring itself remains UI-only
Known gotchas
Rules cannot be created, updated, or deleted via API — only the two list endpoints exist; authoring stays in the Front UI
The rules:read scope is separate from conversations/drafts scopes and must be explicitly granted to the token or app
There is no documented filter/search parameter beyond scoping by company vs. a specific teammate
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?