Connect MX Technologies to Definable AI

About MX Technologies

MX Technologies is a productivity tool. Connect it to Definable AI with one-click OAuth2 — no API keys or custom code required.

What you can automate with MX Technologies

Use Definable AI's agent platform to trigger workflows from MX Technologies, process results with 50+ AI models, and sync data across 900+ connected apps.

Tools & Actions (40 available)

• Create Partner Account: Create a new user (partner account) in the MX Platform. Users represent end-users in your application and are required before creating members, accounts, or accessing financial data. Use this tool to provision a new user record in MX.
• Create User with SSO Metadata: Create a new MX user with SSO-related metadata. Use this tool to create a user in MX Platform while storing SSO identity provider information in the user's metadata. This allows partners to map MX users to their external SSO system (e.g., Okta, Auth0, Azure AD). The tool stores external_id and external_provider in the user's metadata field, which can be retrieved later to correlate MX users with SSO identities.
• Create account: Creates a manual account for a specified user in MX Platform. Use this tool when you need to: - Add an external/off-platform account that isn't aggregated through MX - Create a test account for development purposes - Track accounts from institutions not supported by MX aggregation Note: Manual accounts do not aggregate data from financial institutions. They are created under the special 'Manual Institution' member and require manual updates for balance and transaction information. Requires: A valid user_guid (obtained from List Users or Create User).
• Create member: Create a member to connect a user to a financial institution. A member represents the relationship between an MX user and a financial institution. For non-OAuth institutions, provide credentials obtained from List Institution Credentials. For OAuth institutions, set is_oauth=true and use the returned oauth_window_uri. Prerequisites: - user_guid from List Users or Create User - institution_code from List Institutions - credentials from List Institution Credentials (for non-OAuth) Test credentials for MX Bank (mxbank): username='mxuser', password='password'
• Disable MX User Account: Disables an MX user account, preventing background updates to accounts and transactions and restricting data access. The user can be re-enabled later via the update user endpoint. Uses MX Platform API: PUT /users/{user_guid} with is_disabled=true.
• Fetch rewards: Initiate rewards aggregation for a specific member. This triggers an async job to gather rewards data (points, miles, etc.) from the member's financial institution. Use List Rewards to retrieve the results after aggregation completes.
• Get configurable widget URL: Retrieve a configurable widget URL for embedding MX widgets (Connect, Transactions, Pulse, etc.). Use this tool to generate a single-use URL for displaying MX widgets to end users. The URL expires after 10 minutes or immediately upon first use, so always request a fresh URL when loading the widget. Requires a valid user_guid (obtained from list_users or create_user actions).
• List Account Numbers by Member: Tool to list account numbers for a specific member. Use after obtaining user and member GUIDs.
• List account owners: Tool to list account owners for a specific member. Returns identity information (name, address, contact details) for all account owners associated with the member's accounts. Requires user_guid and member_guid. Use this to retrieve account holder identity data for verification or compliance purposes.
• List account owners by member: Tool to list account owners for a specific member. Use when you have the user GUID and member GUID.
• List accounts: Tool to list all accounts for a user. Use after confirming the user GUID.
• List budgets: List all budgets for a specific MX user. Budgets track spending limits for categories. Prerequisites: Obtain a valid user_guid from the List Users endpoint first. Note: Budgets are automatically generated based on transaction history or can be manually created. If a user has no budgets, an empty list is returned.
• List categories: Tool to list all categories for a user. Use when you need to fetch both default and custom categories for a given user GUID.
• List challenges: Tool to list MFA challenges for a member. Use when the member is in CHALLENGED state to retrieve prompts to answer.
• List favorite institutions: List the partner's favorite financial institutions, sorted by popularity. Use this tool to retrieve institutions that have been pre-configured as favorites for the partner account. Results are paginated and can be filtered by country. Note: Favorite institutions must be configured by MX - contact MX support to set up favorites.
• List goals: List all financial goals for a specific MX user. Use this to retrieve a paginated list of the user's savings goals, including target amounts, progress, and completion dates. Requires a valid user GUID obtained from the LIST_USERS action.
• List institution credentials: Tool to list credential fields required by a given institution. Use after selecting the institution code; supports optional pagination.
• List institutions: Tool to list financial institutions supported by MX. Use when you need to retrieve available institutions with optional filters like name, country code, or products; supports pagination.
• List member accounts: Tool to list accounts for a specific member. Use when you need to retrieve all accounts associated with a given user and member GUID.
• List members: List all members (financial institution connections) for a specific user. A member represents a connection between a user and a financial institution. Use this tool to retrieve all members linked to a user, including their connection status, aggregation state, and institution details. Useful for checking which accounts are connected, identifying connection issues, or finding member GUIDs for other operations. Returns paginated results with member details and pagination info.
• List rewards: Lists rewards and loyalty program data for a specific member. Returns information about points, miles, and other rewards balances from connected financial institutions. Requires valid user_guid (from List Users) and member_guid (from List Members). Supports pagination for large result sets.
• List statements by member: Retrieve a paginated list of monthly account statements (PDF) for a specific member. Use this tool after obtaining valid user_guid (via LIST_USERS) and member_guid (via LIST_MEMBERS). Statements include bank/credit statements in PDF format. The uri field in each statement can be used to download the actual PDF.
• List taggings: List all taggings for a specific MX user. Taggings are links between custom tags and transactions - they show which labels have been applied to which transactions. Use this when you need to: - See all tag-transaction associations for a user - Find which transactions have been labeled with custom tags - Audit or review a user's transaction categorization Prerequisites: Obtain a valid user_guid from LIST_USERS first.
• List tags: List all custom tags associated with a specific MX user. Tags are labels that can be applied to transactions for organization. Every user has a default 'Business' tag. Returns paginated results. Use this to retrieve tag GUIDs needed for tagging transactions.
• List transactions: Retrieve all financial transactions for an MX user across all their connected accounts and members. Use this tool to get a user's complete transaction history. Supports pagination, date filtering, and optional enhanced data (merchants, geolocations, classifications, repeating transactions). Prerequisites: You need a valid MX user GUID (starts with 'USR-'). Get this from the List Users action.
• List transactions by member: Tool to list transactions for a member. Use when you have valid user and member GUIDs and need their transactions.
• List users: List all users in the MX Platform. Use this to retrieve a paginated list of user accounts with optional filters by ID, email, or disabled status. Each user represents an end user accessing MX Platform through your application. Returns user details including guid (MX identifier), id (partner-defined identifier), email, and account status flags.
• Read FDX account: Retrieve details for a specific account using the FDX 4.6 standard API. This action fetches comprehensive account information including balances, status, and account attributes. It requires an FDX account identifier. AUTHENTICATION: This endpoint requires OAuth Bearer token authentication obtained from the MX Data Access OAuth flow. Basic Auth credentials for the MX Platform API will not work with FDX endpoints. FALLBACK: If FDX endpoints fail and the account_id looks like an MX Platform GUID (starts with 'ACC-' or 'ACT-'), the action will attempt to use the MX Platform API to retrieve the account instead.
• Read account: Tool to retrieve details for a specific account. Use after obtaining valid user and account GUIDs to fetch up-to-date account information.
• Read account balance: Retrieves account details including balance information for a specific account. Returns the account object with current balance, available balance, and other account metadata. Use LIST_USERS to get valid user GUIDs and LIST_ACCOUNTS to get valid account GUIDs before calling this action.
• Read category: Tool to retrieve a default category by GUID. Use after confirming the default category GUID.
• Read institution: Tool to retrieve details for a specific institution by code. Use when you need to get information about a particular financial institution using its unique code.
• Read transaction: Tool to retrieve details for a specific transaction by its GUID. Use when you need to fetch information about a particular transaction for a user.
• Read transaction by account: Tool to retrieve details for a specific transaction by account. Use when you need to fetch information about a particular transaction using user, member, account, and transaction identifiers. Supports optional enhancements like merchant details, geolocations, classifications, and repeating transaction patterns.
• Read transaction rule: Tool to retrieve details for a specific transaction rule by its GUID. Use when you need to fetch information about a particular transaction rule for a user.
• Request Connect Widget URL: Generate a Connect widget URL for a user. Use this to obtain a single-use URL that loads the MX Connect widget, allowing users to link their financial accounts. The URL expires after 10 minutes or upon first use. Note: Despite the name, this action generates a new widget URL rather than listing existing ones.
• Retrieve Audience API Credentials: Tool to retrieve Audience API credentials. Use when obtaining client_id and client_secret for Audience Service authentication before generating an access token. Credentials must be created in the Partner Dashboard (Partner Administrator → Authentication → Audience API Key). The tool prefers explicitly provided values, then falls back to environment variables.
• Update transaction: Tool to update a specific transaction's description. Use when you need to modify the description of an existing transaction.
• Update transaction rules: Tool to update an existing transaction rule. Use when you need to modify how transactions are categorized or described based on pattern matching. Note: Changes to match_description will only be applied to future transactions.
• Update user tagging: Tool to update a tagging for an MX user. Use when you need to change which tag is associated with a specific transaction. A tagging represents the link between a custom tag and a transaction.

How to connect MX Technologies

1. Sign in to Definable AI and go to Apps
2. Search for MX Technologies and click Connect
3. Authorize via OAuth2 — takes under 30 seconds
4. Use MX Technologies actions in your AI agents and workflows