List action executions

Use to find conversations by executed availability, pricing, checkout, booking, custom HTTP/collection or Sheets actions, or investigate activity in one conversation. Omit conversationId for business-wide discovery; filter by actionId and explicit from/to, paginate and deduplicate returned conversationIds. Use get_conversation for matched contacts/metadata and get_action_execution for saved inputs/results. For recent chats with projected action history use list_conversations with actionId; read messages only when requested content or attempts without a recorded action are needed. Use list_conversation_handoffs for human escalation history. Requires action_executions:read. Returns up to 30 saved execution receipts, newest first, ordered by start time then identity. Repeat filters with nextCursor; default seven-day date boundaries remain fixed for pagination. A supplied conversationId must belong to the credential tenant (404 otherwise). Use each entry.receiptId as executionId for detail. Parameters and saved responses never appear here. History covers saved supported gateway executions without historical reconstruction; older, unsupported and background-job executions may be absent. Empty filtered history does not prove no action ran. Technical completion is not proof of booking or delivery.