Connect Mailgun and vTiger CRM

Both apps 33Mailgun 9vTiger CRM 24

• Trigger
  New List

  Triggers when a new mailing list is created in your Mailgun account.

• Trigger
  New Log Data

  Triggers when a new entry appears in your Mailgun account's event logs (accepted, delivered, failed, opened, clicked and other message events).

• Action
  Add route

  Creates an inbound email route in Mailgun that matches incoming messages by a filter expression and forwards, stores or stops them.

• Action
  Delete mailing list member

  Removes a member from a Mailgun mailing list by their email address.

• Action
  Find events

  Returns Mailgun events (accepted, delivered, failed, opened, clicked, and more) for a sending domain that match the filters you supply, such as recipient, message id, event type or time range.

• Action
  List domains

  Returns the sending domains on your Mailgun account, optionally filtered by state, authority or a name search.

• Action
  List mailing list members

  Returns the members of a Mailgun mailing list, with each member's email address, name, custom variables and subscription status. Optionally returns only subscribed or only unsubscribed members.

• Action
  Send Email

  Sends an email from one of your Mailgun sending domains, with plain-text, HTML or stored-template content, optional attachments, tags and delivery options.

• Action
  Send test alert webhook

  Asks Mailgun to send a sample alert notification with dummy data to a webhook address.

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