Connect Geekbot and Pipefy

Both apps 35Geekbot 18Pipefy 17

• Trigger
  New Report

  Triggers when a new standup report is submitted in Geekbot.

• Action
  Add out-of-office period

  Schedules an out-of-office period for you or, if you are an admin, for another team member, covering whole days from the start date to the end date.

• Action
  Add poll

  Creates a one-shot Geekbot poll that posts a question with answer choices to a channel.

• Action
  Add standup

  Creates a new Geekbot standup with its questions, schedule and broadcast channel.

• Action
  Delete report

  Deletes a standup report you authored, removing its broadcast message if one was posted.

• Action
  Delete standup

  Deletes a standup and returns the details of the standup that was removed. You must have permission to edit the standup.

• Action
  Get current user

  Returns the user who owns the connected API key, along with the team they belong to.

• Action
  Get poll

  Returns one poll you created, including its schedule, channel, members and optionally its questions.

• Action
  Get report

  Returns one submitted standup report, including who posted it, when, and the answer to each question.

• Action
  Get standup

  Returns one standup by id, including its schedule, members, broadcast settings and optionally its questions.

• Action
  List out-of-office periods

  Returns out-of-office periods for the team members you can view, ordered by start date, optionally narrowed by users, standups or a date window.

• Action
  List polls

  Returns the active and paused polls you created in Geekbot, optionally filtered by state, channel, anonymity or creation date.

• Action
  List poll votes

  Returns the vote results for a poll, grouped by broadcast and question. Without a date range it covers only the latest broadcast.

• Action
  List reports

  Returns submitted Geekbot standup reports within a time window, optionally filtered by standup or user.

• Action
  List standups

  Returns the active and paused standups visible to the connected user, with optional filters for state, anonymity, channel and creation date.

• Action
  List teams

  Returns the Geekbot team tied to the connected API key, including its users who take part in at least one standup visible to the connected user.

• Action
  Start Report

  Starts a standup immediately so its report questions go out, either to all of its participants or only to the users or emails you name. Returns the vendor's confirmation that the standup was queued.

• Action
  Update standup

  Updates a standup's name, schedule, questions, channel and participants. Returns the updated standup.

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