Connect vTiger CRM to Neon Postgres

Both apps 53vTiger CRM 24Neon Postgres 29

• Trigger
  New Contact (polling)

  Fires when a new Contact is created in vTiger. Polls via VTQL ordered by createdtime.

• Trigger
  New event

  Triggered when any new event is added to your calendar.

• Trigger
  New Lead (polling)

  Fires when a new Lead is created in vTiger. Polls via VTQL ordered by createdtime.

• Trigger
  New opportunity

  Triggered when a new opportunity (Potential) is created in vTiger CRM.

• Trigger
  New organization

  Triggered when any new organization (Account) is added in vTiger CRM.

• Trigger
  New ticket

  Triggered when any new ticket (HelpDesk record) is added.

• Action
  Create Account

  Create an Account (organization) in vTiger. Provide accountname (required) plus any other Account fields.

• Action
  Create Contact

  Create a Contact in vTiger. Provide lastname (required) and any other Contact fields.

• Action
  Create Lead

  Create a Lead in vTiger. Provide lastname and company (required) plus any other Lead fields.

• Action
  Create Opportunity

  Create an Opportunity (Potential) in vTiger. Provide potentialname, related_to, sales_stage, closingdate (required) plus other fields.

• Action
  Create Record

  Create a record in any vTiger module. Pass elementType (module name) and element (a JSON object of field values).

• Action
  Create Ticket

  Create a Help Desk Ticket in vTiger. Provide ticket_title, assigned_user_id (required) plus other fields.

• Action
  Delete Record

  Delete a vTiger record by its id (e.g. 11x123).

• Action
  Describe Module

  Describe the fields and metadata of a vTiger module.

• Action
  Get Current User (me)

  Return the logged-in vTiger user — useful as a connection/auth smoke test.

• Action
  List Accounts

  List Accounts (organizations) via VTQL. Optional limit (default 100).

• Action
  List Contacts

  List Contacts via VTQL. Optional limit (default 100).

• Action
  List Leads

  List Leads via VTQL. Optional limit (default 100).

• Action
  List Modules (listtypes)

  List all accessible vTiger modules (element types).

• Action
  List Opportunities

  List Opportunities (Potentials) via VTQL. Optional limit (default 100).

• Action
  List Tickets

  List Help Desk Tickets via VTQL. Optional limit (default 100).

• Action
  Query (VTQL)

  Run a vTiger Query Language (VTQL) SELECT statement and return matching records.

• Action
  Retrieve Record

  Retrieve a single record by its vTiger record id (e.g. 11x123).

• Action
  Update Record

  Update an existing vTiger record. The element JSON must include the record id and all mandatory fields.

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