Connect Concord CLM and Hjarni

Both apps 34Concord CLM 19Hjarni 15

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

• Trigger
  New Note

  Triggers when a new note is created.

• Action
  Add File to Note

  Attaches a file to an existing note from a URL.

• Action
  Add tag

  Create a tag.

• Action
  Create Folder

  Creates a new folder with a name, parent folder, description, and AI instructions.

• Action
  Create Note

  Creates a new note with a title, body, tags, and folder.

• Action
  Delete folder

  Delete a container.

• Action
  Delete note

  Delete a note (moves to trash).

• Action
  Delete tag

  Delete a tag.

• Action
  Get folder

  Fetch one container by id.

• Action
  Get note

  Fetch one note by id with body, tags, container, files.

• Action
  List notes

  List notes, filter by scope/container_id/tag, paginated.

• Action
  List tags

  List tags.

• Action
  Update folder

  Update a container.

• Action
  Update note

  Update note fields (title, body, tags, container, append_body etc, expected_lock_version).

• Action
  Update tag

  Rename/update a tag.

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