RELATED IDEAS
Return additional data in API rules endpoint
Problem
The fetch rules API endpoint returns only minimal information (name and actions), making it difficult to work with rules programmatically—especially when importing rules via CSV, which require inbox IDs and tag IDs.
Request
Return additional fields in the API response, including inbox IDs, tag IDs, and rule conditions (when/if/then), so rules can be fetched and reimported with complete data.
+1 on this! An update like this would make our integrations with Front more straightforward.
+1 on this. To add to this: AI agents querying rules via the API can only see the
actionsarray (Assume same for MCP). They have no visibility into when or why a rule fires, only what it does. For agents (and integrations generally) trying to audit, explain, or reason about rule behavior, that's the more critical half of the picture. Would love to see triggers and conditions included alongside the inbox/tag IDs already requested here.