Connect Pipefile to Lunch Money

Both apps 33Pipefile 11Lunch Money 22

• Trigger
  File Request Created

  Triggers when a file request is created.

• Action
  Add File Request From Template

  Create a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.

• Action
  Create Contact

  Add to contacts

• Action
  Delete Contact

  Delete a contact by id. Returns 204 No Content on success.

• Action
  Get Contact

  Retrieve one contact by id.

• Action
  Get File Request

  Retrieve detailed information about one file request by id, including contents, items, files, and tracking events.

• Action
  List Contacts

  Retrieve a paginated list of contacts, filterable by name/email/phone partial match.

• Action
  List File Request Templates

  Retrieve the list of file request templates available for creating new file requests, with optional name search.

• Action
  Search File Requests

  Finds all file requests matching this search query (contact name, email, tags, etc).

• Action
  Send Request

  Create and send a new request

• Action
  Update Contact

  Update name/email/phone of an existing contact by id.

• Action
  Create a Manual Account

  Creates a new manually-managed account in Lunch Money.

• Action
  Create a New Category or Category Group

  Creates a new category with the given name. If the is_group attribute is set to true, a category group is created. In this case, up to three child categories may be added to the newly-created category group.

• Action
  Create a New Tag

  Creates a new tag in your Lunch Money budget.

• Action
  Create a New Transaction

  Creates a new transaction with the given details. Amount, and Date are required. Other attributes may also be provided.

• Action
  Delete a Category or Category Group

  Deletes a category. By default this will fail if the category has dependencies such as existing transactions or child categories. Set force to true to delete the category even if it has dependencies.

• Action
  Delete a Manual Account

  Deletes a single manual account in Lunch Money, optionally along with its transactions, rules, recurring items and balance history.

• Action
  Delete a Tag

  Deletes a tag. By default this will fail if the tag has dependencies such as existing transactions or rules. Set force to true to delete the tag even if it has dependencies.

• Action
  Delete a Transaction

  Deletes the transaction with the specified ID. Will fail if the transaction is grouped or split.

• Action
  Get All Categories

  Retrieve all categories and category groups in the Lunch Money account.

• Action
  Get All Manual Accounts

  Retrieve a list of all manually-managed accounts associated with the user's account.

• Action
  Get All Tags

  Retrieves every tag in the Lunch Money account.

• Action
  Get All Transactions

  Retrieve a list of all transactions associated with a user's account. If called with no parameters, this endpoint will return the most recent transactions up to limit number of transactions.

• Action
  Get a Single Category

  Retrieves one category or category group by its ID. For a group, its categories are returned under children.

• Action
  Get a Single Manual Account

  Retrieves the details of the manually-managed account with the specified ID.

• Action
  Get a Single Tag

  Retrieves the details of a single tag by its ID.

• Action
  Get a Single Transaction

  Retrieves the details of the transaction with the specified ID.

• Action
  Get Current User

  Returns the Lunch Money user and budget associated with the connected account's access token.

• Action
  Get Summary

  Retrieves a summary of the budget for a date range: each category's budget configuration and activity, plus optional overall totals, per-period occurrences and the rollover pool.

• Action
  Update an Existing Category or Category Group

  Modifies the properties of an existing category or category group in Lunch Money. Only the fields you fill in are changed. A category cannot be converted into a group or vice versa.

• Action
  Update an Existing Manual Account

  Modifies the properties of an existing manual account in Lunch Money. Only the fields you fill in are changed.

• Action
  Update an Existing Tag

  Updates an existing tag in Lunch Money. Only the properties you fill in are changed.

• Action
  Update an Existing Transaction

  Modifies the properties of an existing transaction. Only the fields you fill in are changed.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.