Connect LassoCRM and vTiger CRM

Both apps 37LassoCRM 13vTiger CRM 24

• Trigger
  New Registrant

  Triggers when a new registrant (lead) is added to your Lasso project.

• Action
  Add Note to Registrant

  Adds a free-text note to a registrant.

• Action
  Create a History Item

  Logs a history item (email, phone call, appointment, visit) on a registrant's timeline.

• Action
  Create Inventory

  Creates an inventory item (unit) in your Lasso project.

• Action
  Create Registrant

  Creates a new registrant (lead) in your Lasso project with their name, email and phone.

• Action
  Delete Inventory

  Deletes an inventory item from your Lasso project.

• Action
  Find Registrants

  Finds registrants matching a name, email, phone or external ID and returns the matches.

• Action
  Get Inventory

  Returns one inventory item (unit) with its status, plan and size.

• Action
  Get Registrant

  Returns a registrant's details (name, primary email and phone, rating, registration date) by their Lasso ID.

• Action
  List Inventory

  Returns every inventory item (units, lots) in your Lasso project.

• Action
  Update and Append to a History Item

  Updates an existing history item on a registrant, such as its subject or full content.

• Action
  Update Inventory

  Updates an inventory item's status, plan or size; fields left blank keep their current values.

• Action
  Update Registrant

  Updates a registrant's personal information such as name, company and contact preference.

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