Connect Bento and Pipefy

Both apps 41Bento 24Pipefy 17

• 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
  Track Subscribe Event

  Subscribes or unsubscribes a Bento subscriber by email.

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

• Trigger
  Done Card

  Triggers when a card is done.

• Trigger
  Moved Card

  Triggers when a card is moved.

• Trigger
  New Card

  Triggers when a new card is created.

• Trigger
  New Database Record

  Triggers when a new record is created.

• Trigger
  Updated Card Field

  Triggers when a card field is updated.

• Trigger
  Updated Record Field

  Triggers when a record field is updated.

• Action
  Create Card

  Creates a card in a Pipefy pipe, filling in its start form fields.

• Action
  Create Record

  Creates a new table record.

• Action
  Delete Card

  Permanently deletes a card from its pipe.

• Action
  Delete Database Record

  Delete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation.

• Action
  Find Card

  Returns the cards in a pipe whose chosen field matches the specified value.

• Action
  Find Database Records

  Find a database records by title.

• Action
  Get Card

  Retrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values.

• Action
  Get Database Record

  Fetch a single database table record by ID via the GraphQL `table_record(id: ID)` query.

• Action
  Move Card

  Moves a Pipefy card to another phase of its pipe.

• Action
  Update Card Field

  Sets a new value on one field of an existing Pipefy card.

• Action
  Update Database Record

  Update a database table record's title/fields via the GraphQL `updateTableRecord(input: {id, title})` mutation.

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