Connect Willo to Lunch Money

Both apps 42Willo 20Lunch Money 22

• Trigger
  List Users

  Triggers when a new user is added to your Willo account.

• Action
  Accept Candidate

  Marks a participant in a Willo interview as Accepted and returns the updated participant. Can also update the participant's name, phone number and custom ID in the same step.

• Action
  Add department

  Creates a new department in your Willo organisation and returns the department, including its key and branding.

• Action
  Add interview from template

  Creates a new interview in Willo from one of your interview templates and returns the new interview.

• Action
  Create Company

  Creates a new company as a child organisation under your Willo organisation, with the owner you name.

• Action
  Create Interview

  Creates a new video interview in Willo with its questions, department, message templates and settings.

• Action
  Delete interview

  Deletes an interview from your Willo account.

• Action
  Delete participant

  Deletes a participant from Willo. Returns whether the deletion was confirmed.

• Action
  Get interview

  Returns a Willo interview by its key, including its questions, owner, department, reviewers, message templates and settings. An error occurs if the interview is not found.

• Action
  Get participant

  Returns a Willo participant (candidate) with their contact details, status, interview, department, scores and answers.

• Action
  Get user

  Returns a Willo user's details, including email, full name, phone, role and status.

• Action
  Invite Someone

  Invites a person to a Willo interview as a participant and returns the new participant with their invite link.

• Action
  List departments

  Returns the departments in your Willo organisation, optionally filtered by name, owner email or owner.

• Action
  List interviews

  Returns the interviews in your Willo account, optionally narrowed by department, owner or a search term, and sorted the way you choose.

• Action
  List message templates

  Returns the message templates (email and SMS) in your Willo account, optionally filtered by title, type or trigger.

• Action
  List participants

  Returns the participants in your Willo account, optionally narrowed to an interview, department or owner, or by a text search.

• Action
  List users

  Returns the users in your Willo account with their key, email and full name.

• Action
  Reject Candidate

  Rejects a candidate by setting the participant's status to Rejected, optionally updating their name, phone or custom ID.

• Action
  Update interview

  Updates an existing interview's details, questions, reviewers, message templates and settings, changing only the values you provide. Returns the updated interview.

• Action
  Update participant

  Updates a participant's name, phone, status (Accepted or Rejected) or your own reference 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.