Connect Feathery and vTiger CRM

Both apps 37Feathery 13vTiger CRM 24

• Trigger
  Data Received

  Triggers when an end user submits or updates data on a Feathery form.

• Trigger
  Form Completion

  Triggers when an end user completes a Feathery form.

• Action
  Create Hidden Field

  Creates a hidden field in your Feathery account.

• Action
  Create or Fetch User

  Creates a Feathery end user with the given ID, or returns the existing user, including its SDK key.

• Action
  Create or Update Submission

  Sets field values for a Feathery user and initializes submissions on the given forms.

• Action
  Delete User

  Deletes a Feathery end user and their submissions.

• Action
  Get User Field Data

  Returns every field value a Feathery user submitted across forms.

• Action
  Get User Form Session

  Returns a Feathery user's form session: every form they are working on and their progress.

• Action
  List Document Templates

  Returns document templates uploaded by your Feathery team, optionally filtered by name or tags.

• Action
  List Forms

  Returns your Feathery forms, optionally filtered by tags or active status.

• Action
  List Form Submissions

  Returns submissions for a Feathery form, optionally filtered by user, completion and update time.

• Action
  List Hidden Fields

  Returns all hidden fields in your Feathery account.

• Action
  List Users

  Returns your Feathery end users, optionally filtered by creation time or a field value.

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