Skip to content

Transaction rules engine V1 #1900

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 61 commits into from
Apr 18, 2025
Merged

Transaction rules engine V1 #1900

merged 61 commits into from
Apr 18, 2025

Conversation

zachgoll
Copy link
Collaborator

@zachgoll zachgoll commented Feb 25, 2025

This PR introduces a basic rules engine that allows users to define "triggers" and "actions" that Maybe will automatically detect and apply to transactions during the "Sync" process:

CleanShot 2025-02-25 at 11 13 01

Initial scope

While a Rule may eventually apply to several models, this PR is a minimal implementation that focuses on:

  • Transaction records
  • Active/inactive rules
  • Effective dates
  • Basic AND/OR trigger condition logic
  • Categorization and tagging rules based on:
    • Text matching
    • Transaction values

Further rule templates will be added in the future, but these represent the highest impact rules for most users.

Self hosted vs. Hosted

Both versions of the app will have rules, but the hosted version will have additional controls that allow users to assign rules based on Plaid (data provider) info in addition to basic text/account/type matching.

@zachgoll zachgoll force-pushed the zachgoll/rules-engine-v1 branch from 8d1eb3f to 3bc0c18 Compare April 2, 2025 12:33
@zachgoll zachgoll marked this pull request as ready for review April 17, 2025 18:41
@zachgoll zachgoll merged commit 297a695 into main Apr 18, 2025
5 checks passed
@zachgoll zachgoll deleted the zachgoll/rules-engine-v1 branch April 18, 2025 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant