Connect Cvent to Resend

Both apps 45Cvent 17Resend 28

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

• Action
  Add Contact to Segment

  Adds a contact to a Resend segment. You can identify the contact by its ID or email address.

• Action
  Add Suppression

  Adds an email address to your Resend suppression list so no further mail is sent to it.

• Action
  Cancel Email

  Cancels a scheduled Resend email that has not been sent yet.

• Action
  Create API Key

  Creates a new Resend API key. The key itself is returned once, so store it right away.

• Action
  Create Contact

  Creates a contact in Resend. Returns the new contact's ID.

• Action
  Create Domain

  Adds a sending domain to Resend. Returns the DNS records you need to add at your domain host to verify it.

• Action
  Create Segment

  Creates a new segment in Resend for grouping contacts.

• Action
  Delete API Key

  Deletes a Resend API key so it can no longer be used.

• Action
  Delete Contact

  Deletes a contact from Resend. You can identify the contact by its ID or email address.

• Action
  Delete Domain

  Removes a sending domain from Resend.

• Action
  Delete Segment

  Deletes a segment from Resend. The contacts themselves are not deleted.

• Action
  List API Keys

  Returns the API keys on your Resend account, with each key's name and when it was last used. The key values themselves are never returned.

• Action
  List Contacts

  Returns the contacts in your Resend account, optionally limited to one segment.

• Action
  List Domains

  Returns the sending domains on your Resend account and each one's verification status.

• Action
  List Segments

  Returns the contact segments in your Resend account.

• Action
  List Sent Emails

  Returns the emails you have sent through Resend, newest first, with each email's id, sender, recipients, subject, send time and latest delivery event. Supports paging before or after a given email id.

• Action
  List Suppressions

  Returns the email addresses on your Resend suppression list, showing for each one the address, why it was suppressed (bounce, complaint or added manually), the email that triggered it and when it was added.

• Action
  Remove Contact From Segment

  Removes a contact from one of your Resend segments. Identify the contact by its ID or by its email address, and name the segment to take it out of. The contact itself is not deleted.

• Action
  Remove Suppression

  Takes an email address off your Resend suppression list so you can send to it again. Identify it by the suppression ID or by the email address itself.

• Action
  Retrieve Contact

  Returns one contact from your Resend audience, including their name, email address, whether they have unsubscribed, when they were added, and any custom properties stored on them. Look the contact up by its ID or by its email address.

• Action
  Retrieve Domain

  Returns one of your Resend sending domains, including its name, verification status, sending region, tracking settings and the DNS records it needs with each record's current status.

• Action
  Retrieve Segment

  Returns one of your Resend segments by its ID, with the segment's name and when it was created.

• Action
  Retrieve Sent Email

  Returns one email you sent through Resend, with its sender, recipients, subject, HTML and text body, tags, send time and latest delivery event.

• Action
  Send Batch Emails

  Sends up to 100 emails through Resend in a single call. Give it a list of emails, each with a sender, recipients, subject and body, and it returns the id of every email it created.

• Action
  Send Email

  Sends an email through Resend. Set the sender, recipients and subject, provide an HTML or plain text body, and optionally add CC/BCC, reply-to, attachments, tags or a send time.

• Action
  Update Contact

  Updates a contact in your Resend audience. Identify the contact by ID or email address, then change the name, the subscribed/unsubscribed state, or the custom properties. Anything you leave blank stays as it is.

• Action
  Update Email

  Reschedules an email you already queued in Resend, moving it to a new send date and time. Only emails that have not gone out yet can be changed.

• Action
  Verify Domain

  Asks Resend to re-check the DNS records for one of your sending domains and start verifying it. Verification runs in the background, so the domain shows as pending until it finishes.

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