Connect vTiger CRM to Updown.io

Both apps 34vTiger CRM 24Updown.io 10

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

• Action
  Create Check

  Creates a new uptime check in updown.io for a URL you want monitored, and returns the created check including its token.

• Action
  Create Recipient

  Adds a new alert recipient (email, SMS, webhook, Slack-compatible or Microsoft Teams) to your updown.io account and returns the created recipient.

• Action
  Delete Check

  Deletes an uptime check from updown.io by its token.

• Action
  Delete Recipient

  Removes an alert recipient from your updown.io account by its id.

• Action
  Get Check

  Returns a single updown.io uptime check by its token, including its current status, uptime and settings.

• Action
  Get Check Metrics

  Returns performance metrics for an updown.io check over a period — uptime, apdex, request counts and average timings, optionally grouped by time or monitoring location.

• Action
  List Checks

  Returns every uptime check on your updown.io account with its current status and settings.

• Action
  List Downtimes

  Returns the recorded outages for an updown.io check, newest first, with the reason, start and end times and duration of each.

• Action
  List Recipients

  Returns every alert recipient on your updown.io account — email addresses, phone numbers, webhooks and chat integrations.

• Action
  Update Check

  Updates the settings of an existing updown.io uptime check — its URL, name, interval, threshold, alert muting and more. Anything left blank keeps its current value.

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