Connect Repsly to Mx Technologies

Both apps 54Repsly 19Mx Technologies 35

• Trigger
  New Audit With Items

  Triggers when a new retail audit is submitted in Repsly, returning the audit with its client, representative and audited items.

• Trigger
  New client note

  Triggers when a representative adds a new note to a client in Repsly.

• Trigger
  New Client With Details

  Triggers when a new client is added in Repsly, returning the client's code, name, address, contact details, territory and assigned representative.

• Trigger
  New Form With Details

  Triggers when a representative submits a new form in Repsly, returning the form with its client, representative and answers.

• Trigger
  New Order

  Triggers when a new order or other sales document is created in Repsly, returning the document with its client, representative, status and line items.

• Trigger
  New photo

  Triggers when a new photo is taken in Repsly, returning the photo URL, note, client and representative.

• Trigger
  New Visit Start

  Triggers when a representative starts a new client visit in Repsly, returning the visit's client, representative, start time and location.

• Trigger
  New Workday Start

  Triggers when a representative starts a new workday in Repsly, returning the workday's start time, mileage and representative.

• Action
  Add account

  Creates or updates a place account in Repsly by its unique code.

• Action
  Add pricelist

  Adds a product with its price to an existing Repsly pricelist (or updates it), via an asynchronous import job.

• Action
  Add schedule

  Creates or updates a visit schedule in Repsly for a client and representative.

• Action
  Add user

  Creates a user in Repsly, or updates the existing user with the same code.

• Action
  Create Client

  Creates a client in Repsly, or updates it when the code already exists. Repsly processes the import in the background and returns the import job ID.

• Action
  Create Product

  Creates a product in Repsly, or updates it when the code already exists. Repsly processes the import in the background and returns the import job ID.

• Action
  Get client

  Returns a single client (place) from Repsly by its client code, including address, contact, territory, representatives and custom attributes.

• Action
  Get import job status

  Returns the status of a Repsly import job, including counts of inserted, updated and invalid rows plus any warnings and errors.

• Action
  List pricelists

  Returns all pricelists in your Repsly account, with their name, default flag and active status.

• Action
  List products

  Returns the products in your Repsly account, with their codes, names, prices, barcodes, packaging and custom attributes.

• Action
  Update sales document status

  Changes the status of a Repsly sales document, such as a purchase order, to another valid status for its document type.

• Action
  Add account

  Creates a manual account for an MX user. Manual accounts sit under the Manual Institution member and never aggregate data from a financial institution.

• Action
  Add budget

  Creates a budget for a category on an MX user.

• Action
  Add category

  Create a custom category for a user.

• Action
  Add goal

  Create a goal for a user.

• Action
  Add member

  Create a member (connection between a user and a financial institution) to start aggregation.

• Action
  Add transaction

  Creates a manual transaction on a manual account belonging to an MX user.

• Action
  Add user

  Creates a new MX user. The returned user guid is what other MX actions (such as Add member) use to identify the user.

• Action
  Aggregate member

  Starts an aggregation for a member, pulling the latest account and transaction data from the connected institution. MX may skip the aggregation if the data was updated recently.

• Action
  Delete account

  Delete a manually created account.

• Action
  Delete budget

  Deletes a budget belonging to an MX user.

• Action
  Delete category

  Delete a custom category.

• Action
  Delete goal

  Delete a goal.

• Action
  Delete member

  Delete a member connection.

• Action
  Delete user

  Delete a user.

• Action
  Get account

  Read an account's attributes.

• Action
  Get budget

  Retrieves a specific budget for an MX user.

• Action
  Get institution

  Read an institution's attributes.

• Action
  Get member

  Read a member's attributes and connection status.

• Action
  Get merchant

  Returns information about a particular merchant, such as its logo, name, and website.

• Action
  Get transaction

  Read a transaction's attributes.

• Action
  Get user

  Retrieves the attributes of a specific MX user.

• Action
  List accounts

  Lists all accounts belonging to an MX user. Returns up to 1000 accounts in one call.

• Action
  List categories

  Lists all categories for an MX user, including default and custom categories.

• Action
  List goals

  Lists all goals for an MX user.

• Action
  List institutions

  Lists financial institutions available through MX, optionally filtered by name, country and supported product.

• Action
  List members

  List all members belonging to a user.

• Action
  List merchants

  Lists merchants in the MX system, optionally filtered by a name substring.

• Action
  List transactions

  List all transactions for a user.

• Action
  Update account

  Updates an account belonging to a member. Manual accounts can have every field updated; aggregated accounts only accept changes to Is Business, Is Hidden and Metadata.

• Action
  Update budget

  Update a specific budget.

• Action
  Update category

  Update a custom category.

• Action
  Update goal

  Updates an existing savings or payoff goal for an MX user. Only the fields you fill in are changed.

• Action
  Update member

  Updates a member's credentials, id, metadata, background aggregation setting or use cases. At least one value to update must be supplied.

• Action
  Update transaction

  Update a transaction's category, description, or other editable attributes.

• Action
  Update user

  Update a user's attributes.

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