Connect CompanyHub and vTiger CRM

Both apps 37CompanyHub 13vTiger CRM 24

• Trigger
  New Company

  Triggers when a new company is added in CompanyHub.

• Trigger
  New Contact

  Triggers when a new contact is created in CompanyHub.

• Trigger
  New Deal

  Triggers when a new deal is created in CompanyHub.

• Trigger
  New Record (Custom Table)

  Triggers when a new record is added to the CompanyHub table you choose, such as one of your custom tables.

• Trigger
  New Task

  Triggers when a new task is created in CompanyHub.

• Trigger
  Record Updated

  Triggers when a record in the chosen CompanyHub table is created or changed.

• Action
  Create a Record (Custom Table)

  Creates a record in any CompanyHub table, including custom tables, from the field values you supply, and returns the new record's ID.

• Action
  Create Company

  Creates a new company record in CompanyHub and returns its ID.

• Action
  Create Contact

  Creates a contact in CompanyHub and returns the new contact's ID.

• Action
  Create Deal

  Creates a deal in CompanyHub and returns the new deal's ID.

• Action
  Create Task

  Creates a task in CompanyHub with the given title, type, category, assignee and end time, plus any other Task fields you set.

• Action
  Find Record

  Returns the records in a CompanyHub table (Contact, Company, Deal or a custom table) whose chosen field matches the value you supply.

• Action
  Update Record

  Updates an existing record in a CompanyHub table (Contact, Company, Deal or a custom table), changing only the fields you supply.

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

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