Connect Azure Key Vault and Bento

Both apps 36Azure Key Vault 9Bento 27

• Trigger
  New Secret

  Triggers when a new secret is added to your key vault.

• Action
  Delete Secret

  Deletes a secret and all its versions. If the vault has soft-delete on, the secret can still be recovered until it is purged.

• Action
  Get Deleted Secret

  Returns the details of a secret that was deleted but not yet purged, including when it will be permanently removed.

• Action
  Get Secret

  Returns a secret's value and details, either the latest version or a specific one.

• Action
  List Secrets

  Returns the secrets in your key vault with their details (not their values).

• Action
  Purge Deleted Secret

  Permanently removes a deleted secret so it cannot be recovered and its name can be reused.

• Action
  Recover Deleted Secret

  Restores a deleted secret, with all its versions, before it is purged.

• Action
  Set Secret

  Stores a secret in your key vault. If a secret with that name already exists, a new version of it is created.

• Action
  Update Secret Properties

  Changes a secret's settings (enabled, content type, expiry, tags) without changing its value.

• Trigger
  New Tag

  Triggers when a new tag is created on your Bento site.

• Action
  Add broadcast

  Creates a broadcast email draft in Bento, optionally scheduled and approved for sending to tagged or segmented subscribers.

• Action
  Create Field

  Creates a custom subscriber field on your Bento site.

• Action
  Create or Update User

  Creates a Bento subscriber, or updates the name of an existing one, by email address.

• Action
  Create or Update User and Apply Tag

  Creates or updates a Bento subscriber by email and applies one or more tags, without triggering Flows.

• Action
  Create or Update User and Apply Tag (Trigger Flows)

  Applies a tag to a Bento subscriber (creating them if needed) through an event, so any Flows listening for that tag start.

• Action
  Create Tag

  Creates a tag on your Bento site.

• Action
  Delete tag

  Discards a tag in Bento by name (running it on an already-discarded tag restores it).

• Action
  Fetch Site Metrics

  Returns your Bento site's user, subscriber and unsubscriber counts.

• Action
  Fetch Subscriber

  Returns a Bento subscriber's details, tags and custom fields by email address.

• Action
  Get email template

  Returns one email template, including its name, subject and HTML content.

• Action
  Get segment

  Returns one segment, including its name, description and filter definition.

• Action
  Import subscribers

  Queues up to 1,000 subscribers for import or update in Bento. Imports do not trigger automations.

• Action
  List Broadcasts

  Returns one page of Bento broadcasts with the chosen status, including their send stats.

• Action
  List Fields

  Returns every custom subscriber field on your Bento site.

• Action
  List segments

  Returns all segments in your Bento site.

• Action
  List sequences

  Returns the sequences on your Bento site, including each sequence's email templates.

• Action
  List Tags

  Returns every tag on your Bento site.

• Action
  List workflows

  Returns all workflows on the Bento site, with their name, status and email templates.

• Action
  Remove Tag from Subscriber

  Removes a tag from a Bento subscriber by email.

• Action
  Send Transactional Email

  Sends an email through Bento to one recipient, optionally as transactional so it reaches unsubscribed people.

• Action
  Track Event

  Records a custom event for a Bento subscriber, optionally updating their profile fields; events can start Flows.

• Action
  Track Subscribe Event

  Subscribes or unsubscribes a Bento subscriber by email.

• Action
  Track Unique Event

  Records a purchase for a Bento subscriber with its value, counted once per order ID.

• Action
  Update email template

  Updates the subject, HTML content, or editor type of a Bento email template.

• Action
  Update Subscriber Field

  Sets one custom field value on a Bento subscriber.

• Action
  Validate Email

  Checks whether an email address looks valid and deliverable.

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