Favro Make integrationAutomate Favro with Make.

You get a new card on a Favro board, filled from whatever the previous module sent. Cards are where your team tracks the work, so this is often the heart of a scenario.

A fresh collection appears in Favro, ready to hold the boards of a new project or client. It saves you setting up the same structure by hand each time a project starts.

Adds a column to a board, which gives your cards a new stage to move into. Handy when a workflow gains a step and several boards must follow.

Posts a comment on a card, so context from another tool lands where your team already reads. The card stays the single place to look.

Sets up a new organization in Favro from a scenario. Few teams need it daily, but it helps when each client or entity gets its own isolated workspace.

Puts a tag on a card, which makes it easy to filter later by client, priority or source. Tags added by Make look like the ones your team adds by hand.

Creates a widget, the Favro element that holds columns and cards, such as a board. Pair it with Create a Collection to build a whole project skeleton in one run.

Removes a card for good, which keeps a board free of duplicates or tasks that no longer apply. Use a search module first to be sure you hit the right one.

Clears away a collection you no longer need, so archived projects stop cluttering the sidebar. It works best at the very end of a closing process.

Takes a column off a board when a stage of your process disappears. The board gets simpler, but read the warning below before you run it.

Erases a comment from a card, useful when a message was posted by mistake or holds something that should not stay visible. The card itself stays untouched.

Pulls a tag off, so filters and views stop showing cards that no longer belong to a category. Nothing else on the card changes.

Removes a whole widget, the heaviest delete in the app. It is meant for full clean-ups, not for tidying a few cards.

Returns one card with its details, so later modules can use more than what the trigger sent. Think of it as opening the card before acting on it.

Reads a single collection, which lets a scenario check where it is working before it creates or changes anything inside. It returns one item, not a list.

Fetches one column, handy when a scenario needs to know a stage's details before it moves a card or posts a status. Its output feeds the next module directly.

Pulls back one comment so its text can travel elsewhere, for example into an email to a client or a line in a log. Only that comment comes back, not the thread.

Reads one organization from Favro. It rarely drives a scenario alone, yet it gives you the organization's details when a flow spans several workspaces.

Returns a single tag, so a scenario can check its details before it adds or removes it on cards. One tag in, one bundle out.

Brings back one widget, such as a board, with its details. It helps a scenario confirm it is writing to the right place before adding columns or cards.

Sends any request to the Favro API with the connection you already set up, which covers what the listed modules do not. You write the request yourself, so it suits someone at ease with API docs.

Changes an existing card, and it can also commit the card to another widget, which is how a card travels from one board to the next. Most status flows rely on this one.

Edits a collection that already exists, so its details stay in line with the project it represents. No need to rebuild it when something changes.

Modifies a column on a board while keeping its cards in place. That makes it the safe choice when a stage is renamed rather than removed.

Rewrites a comment already posted on a card. A scenario can keep one status comment current instead of stacking a new one at every change.

Adjusts an organization's details from a scenario, which keeps Favro aligned with the source of truth your company uses. It touches the organization, not its boards.

Edits an existing tag, so every card that carries it shows the change. It avoids deleting and recreating the tag, which would strip it from cards.

Changes a widget that already exists, such as a board's details, without touching the columns and cards inside. It keeps structure and content separate.

Attaches a file to a card, so the contract, the brief or the screenshot sits next to the task. PNG and JPG images wider than 400 pixels get a thumbnail on the card.

Adds a file to a comment instead of the card itself, which keeps each attachment tied to the message that explains it. Wide PNG and JPG files, over 400 pixels, get a thumbnail.

Returns the cards shared with your account, one bundle per card, so each can be written to a sheet or checked by later modules. Results come back page by page.

Gives you every collection your account can see, each as its own bundle. It is the starting point for any overview of projects across Favro.

Reads all the columns of one widget, in pages, which shows you the stages of a board. Pair it with List Cards to rebuild a board's picture outside Favro.

Brings back the comments that match what you ask for, spread over pages. Handy to archive a discussion or send the full thread to someone outside Favro.

Returns every organization available to your account. With several workspaces, it is the way for a scenario to go through each one in turn.

Collects the tags that match your settings, page by page. It shows which labels exist before a scenario adds or removes any, so you avoid near duplicates.

Lists the widgets shared with your account, in pages, so a scenario can find every board it is allowed to touch. Each widget arrives as a separate bundle.