Connect Cvent and ilert

Both apps 30Cvent 17ilert 13

• Trigger
  Trigger on New And/Or Updated Attendees

  Triggers when an attendee is registered or an existing attendee record is updated in Cvent.

• Trigger
  Trigger on New And/Or Updated Contacts

  Triggers when a Cvent contact is created or updated.

• Trigger
  Trigger on New And/Or Updated Events

  Triggers when an event is created or updated in your Cvent account.

• Trigger
  Trigger on New Attendee Activities

  Triggers when an attendee performs a new activity (such as registering, checking in or attending a session) in a Cvent event.

• Action
  Create a New Cvent Attendee

  Adds an existing Cvent contact to an event as an attendee, either inviting them or registering them directly.

• Action
  Create a New Cvent Contact

  Creates a new contact in your Cvent address book.

• Action
  Delete contact

  Deletes a contact from your Cvent address book.

• Action
  Find an Attendee

  Finds Cvent event attendees by email address, optionally within one event.

• Action
  Find an Event

  Finds Cvent events whose title matches the one you supply and returns the first match.

• Action
  Get attendee

  Returns a single Cvent attendee by its id, including contact, event and registration details.

• Action
  Get contact

  Returns a single Cvent contact by its id.

• Action
  Get event

  Returns a single Cvent event by its id, including its full details.

• Action
  List events

  Returns the events in your Cvent account, optionally filtered.

• Action
  List sessions

  Returns the event sessions in your Cvent account, optionally filtered.

• Action
  List speakers

  Returns the speakers in your Cvent account, optionally filtered by event or modification date.

• Action
  Update a Cvent Contact

  Updates an existing contact in Cvent's address book.

• Action
  Update attendee

  Updates an existing attendee's registration details in a Cvent event.

• Trigger
  New or Updated Incident

  Triggers when an incident (alert) on the chosen ilert alert source is created or changes: assigned, escalated, accepted, raised, commented on, resolved, or a responder is added or removed.

• Action
  Accept Incident

  Accepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert.

• Action
  Add Alert

  Creates an alert in ilert on the chosen alert source, which then escalates according to the source's escalation policy (or a policy or responders you specify).

• Action
  Add maintenance window

  Creates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time.

• Action
  Create Incident

  Creates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified.

• Action
  Find User on Call

  Finds the user currently on call for an on-call schedule, along with the start and end of their current shift. Returns found=false when nobody is on call.

• Action
  Get alert

  Returns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders.

• Action
  Get incident

  Returns a single ilert incident by its id, including its status, severity, affected services and responders.

• Action
  Get maintenance window

  Fetches a maintenance window by ID. An error occurs if the maintenance window is not found.

• Action
  List Alert Sources

  Returns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy.

• Action
  List incidents

  Returns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date.

• Action
  List users

  Returns the users in your ilert account, with their name, email, role and contact settings.

• Action
  Resolve Incident

  Resolves an ilert alert (formerly called an incident), closing it and stopping further escalation.

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