get_recurring_transactions
Read-only
Detect recurring payments and subscriptions by combining pattern analysis with Copilot's built-in subscription tracking.
Instructions
Identify recurring/subscription charges. Combines two data sources: (1) Pattern analysis - finds transactions from same merchant with similar amounts, returns estimated frequency, confidence score, and next expected date. (2) Copilot's native subscription tracking - returns user-confirmed subscriptions stored in the app. Both sources are included by default for comprehensive coverage.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| min_occurrences | No | Minimum number of occurrences to qualify as recurring (default: 2) | |
| period | No | Period to analyze (default: last_90_days). Options: this_month, last_month, last_7_days, last_30_days, last_90_days, ytd, this_year, last_year | |
| start_date | No | Start date (YYYY-MM-DD) | |
| end_date | No | End date (YYYY-MM-DD) | |
| include_copilot_subscriptions | No | Include Copilot's native subscription tracking data (default: true). Returns copilot_subscriptions array with user-confirmed subscriptions. | |
| name | No | Filter by name (case-insensitive partial match). When filtering, returns detailed view with additional fields like min_amount, max_amount, match_string, account info, and transaction history. | |
| recurring_id | No | Filter by exact recurring ID. When filtering, returns detailed view with additional fields like min_amount, max_amount, match_string, account info, and transaction history. |