Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Vtiger

CRM software for sales, marketing, and support teams

CategorySales And Crm
Authenticationcustom
Version1.4.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Vtiger with Flows360

CRM software for sales, marketing, and support teams

Use the Vtiger connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 8 actions and 1 trigger.

Available actions

  • Create Record
  • Get Record
  • Update Record
  • Delete Record
  • Query Records
  • Search Records
  • Custom API Call (Deprecated)
  • Custom API Call

Available triggers

  • New or Updated Record

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Vtiger
  • Package: @activepieces/piece-vtiger@1.4.0
  • Exact artifact digest: sha256:d300215be30321831ffecad26e7a6100b7b6e5b562a062c168fa8a2ce801449f
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Record (create_record), Create a Record Classification: read.
  • Get Record (get_record), Get a Record by value Classification: read.
  • Update Record (update_record), Update a Record Classification: read.
  • Delete Record (delete_record), Delete a Record Classification: read.
  • Query Records (query_records), Query records by SQL statement. Classification: read.
  • Search Records (search_records), Search for a record. Classification: read.
  • Custom API Call (Deprecated) (make_api_call), Performs an arbitrary authorized API call. (Deprecated) Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New or Updated Record, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects9
Supported actions8
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • VTiger Instance URL Required
  • Username Required
  • Access Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Record Yes No Create a Record
Get Record Yes No Get a Record by value
Update Record Yes No Update a Record
Delete Record Yes No Delete a Record
Query Records Yes No Query records by SQL statement.
Search Records Yes No Search for a record.
Custom API Call (Deprecated) Yes No Performs an arbitrary authorized API call. (Deprecated)
Custom API Call Yes No Make a custom API call to a specific endpoint
New or Updated Record Yes No polling trigger declared by the pinned package.

Supported actions

Create Record · Read

Create a Record

create_record · Risk: low · Retry: safe

Inputs

  • elementType · string · Required, The module / element type
  • record · object · Required, Add new fields to be created in the new record
Get Record · Read

Get a Record by value

get_record · Risk: low · Retry: safe

Inputs

  • elementType · string · Required, The module / element type
  • record · object · Required, Add new fields to be created in the new record
Update Record · Read

Update a Record

update_record · Risk: low · Retry: safe

Inputs

  • elementType · string · Required, The module / element type
  • id · string · Required, The record's id
  • record · object · Required, Add new fields to be created in the new record
Delete Record · Read

Delete a Record

delete_record · Risk: low · Retry: safe

Inputs

  • elementType · string · Required, The module / element type
  • record · object · Required, Add new fields to be created in the new record
Query Records · Read

Query records by SQL statement.

query_records · Risk: low · Retry: safe

Inputs

  • query · string · Required, Enter the query statement, e.g. SELECT count(*) FROM Contacts;
Search Records · Read

Search for a record.

search_records · Risk: low · Retry: safe

Inputs

  • elementType · string · Required, The module / element type
  • fields · object · Required, Enter your filter criteria
  • limit · number · Optional, Enter the maximum number of records to return.
Custom API Call (Deprecated) · Read

Performs an arbitrary authorized API call. (Deprecated)

make_api_call · Risk: low · Retry: safe

Inputs

  • method · string · Required, Select the HTTP method you want to use
  • url · string · Optional, Absolute URL or path. If a relative path is provided (e.g., /me, /listtypes, /describe), it will be called against the REST base.
  • urlPath · string · Optional, Deprecated. Use 'URL' instead. API endpoint's URL path (example: /me, /listtypes, /describe)
  • headers · object · Optional, Enter the desired request headers. Skip the authorization headers
  • data · object · Optional, Enter the data to pass. if its POST, it will be sent as body data, and if GET, as query string
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New or Updated Record · Poll

Triggers when a new record is introduced or a record is updated.

Inputs

  • elementType · string
  • watchBy · string
  • syncType · string
  • limit · number

Setup

Setup

  1. Add the Vtiger connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • VTiger Instance URL (instance_url), required.
  • Username (username), required.
  • Access Key (password), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-vtiger@1.4.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 8 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Vtiger connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-vtiger@1.4.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com