Connect Concord CLM to Neon Postgres

Both apps 48Concord CLM 19Neon Postgres 29

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

  Create a new branch in a Neon project.

• Action
  Add compute endpoint

  Creates a compute endpoint (a Neon compute instance) on a branch of a Neon project. A branch can have one read-write endpoint and multiple read-only endpoints.

• Action
  Add database

  Creates a new Postgres database in a Neon project branch, owned by an existing role.

• Action
  Add project

  Creates a new Neon Postgres project with its default branch, database, role and compute, and returns the project along with its connection details.

• Action
  Add role

  Creates a Postgres role in the specified Neon project branch. Connections to the branch's active compute are dropped while the change applies.

• Action
  Delete branch

  Delete a branch by project_id and branch_id.

• Action
  Delete compute endpoint

  Deletes a compute endpoint from a Neon project. Existing connections to the compute are dropped. If the compute does not exist or was already deleted, the step still succeeds with an empty result.

• Action
  Delete database

  Deletes the specified database from a branch of a Neon project.

• Action
  Delete project

  Deletes a Neon project and all its branches, compute endpoints, databases and roles. The project can be recovered within 7 days.

• Action
  Delete role

  Deletes the specified Postgres role from a Neon branch.

• Action
  Get branch

  Retrieves details of a branch in a Neon project.

• Action
  Get compute endpoint

  Retrieve details about a compute endpoint.

• Action
  Get connection URI

  Retrieve a Postgres connection URI for a database/role/branch/endpoint combination.

• Action
  Get database

  Retrieves details of a database on a Neon project branch.

• Action
  Get project

  Retrieves the details of a Neon project, including its settings, compute configuration, history retention, owner and current usage metrics.

• Action
  Get role

  Retrieves details about a Postgres role (user) on a Neon branch.

• Action
  Get role password

  Retrieves the password for a Postgres role on a Neon branch.

• Action
  List branches

  Retrieve a list of branches for a Neon project.

• Action
  List compute endpoints

  Lists the compute endpoints (Neon compute instances) in a project.

• Action
  List databases

  Lists the databases on a branch of a Neon project.

• Action
  List operations

  Lists the operations (asynchronous actions such as starting a compute or creating a branch) Neon performed on a project. Operations older than 6 months may no longer be available.

• Action
  List projects

  Lists the Neon projects accessible to the connected account, optionally filtered by name/ID or organization.

• Action
  List roles

  Lists the Postgres roles on a Neon project branch.

• Action
  Start compute endpoint

  Start (resume) a suspended compute endpoint.

• Action
  Suspend compute endpoint

  Suspends the specified Neon compute endpoint (scales it to zero).

• Action
  Update branch

  Update a branch's properties (e.g. name, protected) by project_id and branch_id.

• Action
  Update compute endpoint

  Updates an existing compute endpoint in a Neon project by ID.

• Action
  Update database

  Updates the name or owner of a database on a Neon project branch.

• Action
  Update project

  Update settings for a Neon project by project_id.

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