Connect Concord CLM to Mx Technologies

Both apps 54Concord CLM 19Mx Technologies 35

• Trigger
  New agreement

  Triggers when a new agreement appears in the selected Concord organization.

• Action
  Add agreement

  Creates a new agreement in a Concord organization, either as a blank draft, template or contract, or from an existing template or contract. Returns the new agreement's identifiers.

• Action
  Add attachment

  Uploads a file and attaches it to a Concord agreement, and returns the ID of the new attachment.

• Action
  Add folder

  Creates a new folder inside an existing folder of a Concord organization and returns the new folder.

• Action
  Add member to agreement

  Invites a person to an agreement by email with the chosen permission level and sends them an invitation message. Returns the agreement's id, unique identifier and status.

• Action
  Create a New Document From a Template

  Creates a new Concord document from an automated template, filling in its variables and optionally inviting people to it.

• Action
  Create an Executed Document

  Creates an agreement in Concord with the status of an executed contract, rather than a draft or template. Returns the new agreement's identifiers.

• Action
  Create webhook - Document Fully Approved

  Creates a Concord webhook integration that calls the given URL when an agreement is fully approved.

• Action
  Create webhook - Document Fully Signed

  Creates a Concord webhook integration that calls the given address when an agreement is fully signed.

• Action
  Create webhook - Signature Provided

  Creates a Concord webhook integration that calls the given address whenever a new signature is added to an agreement.

• Action
  Delete agreement

  Permanently deletes an agreement from a Concord organization.

• Action
  Get agreement

  Returns one Concord agreement by its UID, including its title, status, folder, tags, permission and creation details. An error occurs if the agreement is not found.

• Action
  List agreements

  Returns the agreements in a Concord organization's inbox, filtered by stage and optionally by creator, tags, dates, parties and search text.

• Action
  List automated templates

  Returns the automated templates available in a Concord organization, with each template's id, title and description.

• Action
  List folders

  Returns the folder tree of a Concord organization: the root folder with its nested subfolders, access settings and document counts.

• Action
  List organizations

  Returns every Concord organization the connected user belongs to, including each organization's name, subscription, and the user's role in it.

• Action
  Move agreement

  Moves an agreement into a different folder in a Concord organization.

• Action
  Request signature

  Requests signatures on an agreement from its signers. Colleagues are added to the agreement, external signers are emailed an invitation, and when a signing order is enabled the request goes to the next signer in that order.

• Action
  Update agreement

  Updates the status of an existing Concord agreement, setting it to Signing or Broken.

• 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.