Moneylogz

Moneylogz for Google Sheets API Documentation for Zapier Integration

Overview

The Moneylogz for Google Sheets API allows users to integrate their Moneylogz account with Zapier to automate tasks related to financial transactions and account management. This documentation outlines the necessary details for authentication, triggers, and actions supported by the integration.

Authentication

Method: OAuth 2.0

Moneylogz for Google Sheets uses OAuth 2.0 for authentication, allowing users to log in with their Moneylogz credentials. This ensures secure and seamless access to your Moneylogz account data via the Zapier integration.

Steps:

1. Users will be prompted to log in with their Moneylogz credentials.
2. Upon successful authentication, an access token will be generated, allowing Zapier to interact with the Moneylogz API on behalf of the user.

Trigger: New Transactions

Description: This trigger is activated whenever new transactions are available in the user’s connected financial accounts.

Inputs:

• Account (Required): The financial account to monitor for new transactions.
• Sub Accounts (Optional): Specific sub-accounts to monitor. If not specified, all sub-accounts are included by default.
• Multiple Transactions (True/False): Determines how transactions are handled.
  • True: All available transactions will be handled at once.
  • False (default value): Each transaction will emit a separate Zap.

Output: A list of new transaction(s) .

Field Definitions for New Transactions Trigger

• amount: The settled value of the transaction, denominated in the transaction’s currency. Positive values indicate money outflow (e.g., debit card purchases), while negative values indicate money inflow (e.g., refunds, deposits).
• date: The date the transaction occurred or posted, returned in ISO 8601 format (YYYY-MM-DD).
• account_name: The name of the account where the transaction occurred.
• merchant_name: The human-readable name of the merchant involved in the transaction, enriched by the service provider (Plaid).
• name: The description or name of the transaction, typically the same as the merchant name for purchases.
• country: The ISO 3166-1 alpha-2 country code where the transaction occurred.
• state: The region or state where the transaction occurred.
• city: The city where the transaction occurred.
• category_id: A numeric ID representing the category to which the transaction belongs.
• category: A hierarchical array of categories classifying the transaction.
• sub_category: A more specific classification within the main category.
• account_owner: The name of the account owner. This is typically not populated unless dealing with sub-accounts.
• authorized_date: The date when the transaction was authorized, often used for posted transactions.
• authorized_datetime: The date and time when the transaction was authorized, in ISO 8601 format.
• check_number: The check number associated with the transaction, if applicable.
• iso_currency_code: The ISO-4217 currency code of the transaction.
• merchant_entity_id: A unique ID generated by Plaid, mapping to the merchant.
• payment_channel: The method by which the payment was made, such as online, in store, or other.
• pending: Indicates if the transaction is pending or unsettled.
• pending_transaction_id: The ID of the associated pending transaction, if applicable.
• transaction_code: A code identifying the type of transaction, relevant for European institutions.
• transaction_id: The unique ID of the transaction.
• website: The website associated with the transaction, if available.
• mask: The last 2-4 alphanumeric characters of the account’s official account number.

Example Output:

[{
“date”: “2024-08-05”,
“merchant_name”: “Uber”,
“name”: “Uber 072515 SF**POOL**”,
“account_name”: “Plaid Checking”,
“amount”: -6.33,
“iso_currency_code”: “USD”,
“country”: “”,
“state”: “”,
“city”: “”,
“category_id”: “22016000”,
“category”: “Travel”,
“sub_category”: “Taxi”,
“account_owner”: null,
“authorized_date”: “2024-08-04”,
“authorized_datetime”: null,
“check_number”: null,
“merchant_entity_id”: “eyg8o776k0QmNgVpAmaQj4WgzW9Qzo6O51gdd”,
“payment_channel”: “online”,
“pending”: false,
“pending_transaction_id”: null,
“transaction_code”: null,
“transaction_id”: “3jJqw7Kw41fZ1N93m6EVHEXdGkBp75cZlnpjq”,
“website”: “uber.com”,
“mask”: “0000”
}]

Actions

1) Get Accounts

Description: Retrieves a list of all connected financial accounts associated with the user’s Moneylogz account.

Inputs: None

Output: A list of connected accounts.

Field Definitions for Get Accounts Action

• id: A unique identifier for the account.
• name: The name of the financial institution.
• title: The name or label given to the account by the user.
• status: The current status of the account (e.g., active, inactive).

Example Output: