Connect FormHug and vTiger CRM

Both apps 36FormHug 12vTiger CRM 24

• Trigger
  New Or Updated Submission

  Triggers when a submission is created or edited on the chosen form.

• Action
  Add entry

  Creates a new entry (submission) on one of your FormHug forms.

• Action
  Add folder

  Creates a new folder for organizing forms, at the root or inside an existing folder.

• Action
  Add form

  Creates a new FormHug form, optionally with initial questions, locale, timezone, folder and header theme.

• Action
  Get current user

  Returns the FormHug user associated with the connected account, including their billing account and current subscription plan.

• Action
  Get entry

  Returns one submitted entry of a form, including every answer keyed by the form field's API code.

• Action
  Get form

  Returns a form's details, including its name, settings, folder and the full list of its fields.

• Action
  List entries

  Returns the entries (submissions) of one of your forms, optionally filtered and sorted.

• Action
  List folders

  Returns all folders owned by the connected FormHug user, newest first.

• Action
  List forms

  Returns the forms you created or that were shared with you, optionally filtered by name or folder.

• Action
  Update entry

  Updates an existing entry on a form. Only the fields you supply change; all other answers stay as they are.

• Action
  Update form

  Updates a form's name, description, locale, timezone, layout or question list. Only the values you provide are changed.

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