Pipefy Strawberry

Cards checked against table records, in one pass

A companion works the 15 operations your Pipefy account exposes. It can update a table and update a table record, and every one of those waits on an approval card showing the card before it changes.

Open the card. Check it against something else. Write the change. Move to the next one. That is the Pipefy afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a card until you approve it.

What it can do is exactly what Pipefy exposes to an account you authorise and nothing beyond it: 15 operations, 7 reads and 8 writes. In practice that means it can update a table, update a table record and update a card, and work across the cards, table records and card fields.

The Pipefy API stops at Pipefy. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.

Which Pipefy cards does a companion see?

7 of the 15 operations are reads.

Your account, not a guess at it: a companion can look up table by ID, look up pipe by ID and look up phase by id, and the full list below is the whole list, with nothing inferred from Pipefy's documentation.

The cards are what most of this inventory is about, alongside the table records. A companion can hold all 15 of these operations and forty open tabs in the same pass, which is how an afternoon of Pipefy admin becomes a queue you review.

  • Look Up Table by ID
  • Look up Pipe by ID
  • Look Up Phase By Id
  • Look up Card by ID
  • Get Table Records
  • Get Current User
  • Get All Cards

Who signs off on a new table record?

All 8 write operations wait for you.

A companion can update a table, update a table record and update a card, and each one is staged on an approval card first: you see the card, the field and the new value before it lands in Pipefy.

Nothing in Pipefy is sent, changed or deleted on your behalf without that click, and a rejected card leaves the card exactly as it was. The gate is the same one on every surface, described at security.

  • Update Table
  • Update Table Record
  • Update Card
  • Update Card Field
  • Delete Card
  • Create Table Record
  • Create Pipe
  • Create Card

Can the cards pass run every Monday?

Yes.

Saved as a routine, the Pipefy cards pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.

The operations playbook catalogues the other recurring shapes of the planning, the Pipefy cards sweep among them, and finished runs are published at real runs.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Yes. Connect your Pipefy account and a companion works 15 operations in it, with every change staged for your approval. You authorise the connection yourself and the credential is held encrypted where Strawberry never receives it.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide