Resources · Claude connector

Claude Fibery connectorWhat Claude can do in your Fibery account.

The Claude Fibery connector exposes 88 tools. 29 read your workspace, from schema to activity history, and 59 write, from a comment to a whole new space, all documented by Fibery. Below: what Claude reads, what it can change or delete, and what nobody can undo.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Claude Fibery connector changes for product teams

A product manager wants a sprint health report before Monday: what is at risk, what is overdue, what shipped. Normally that means opening three boards, filtering, copying numbers into a doc. With the connector she asks Claude. Claude runs the team's saved views, checks the activity log, flags items with no recent updates and writes the summary into a Fibery document.

Ask the workspace anything. schema and schema_detailed show Claude what spaces, databases and fields exist, then query filters, sorts and aggregates records, while search covers names, documents and comments. search_history answers who did what and when, which is how a stand-up recap or release notes get written without digging.

Act on records and documents. create_entities, update_entities and set_state handle the everyday: file a bug, mark it urgent, move features to Done. In documents, insert_document_blocks and replace_block_text write or fix content precisely, and add_inline_comments leaves review notes where they belong.

Reshape the workspace itself. Claude can open a space with create_space, add databases and fields of every type including formulas, build views with create_view, assemble reports, draw on whiteboards and set up automation rules with create_automation. Fibery describes it as Claude doing almost anything you can do yourself.

That power has an edge. delete_entities removes records permanently, and Fibery states it cannot be undone; spaces, databases, fields and automations can be deleted too. Nothing runs by itself from the conversation either: Claude acts when asked, and recurring jobs belong to Fibery automations or to the Fibery n8n integration and the Fibery Make integration.

Vocabulary

Five words before you plug it in

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
Tool
One named action a connector opens to Claude. Claude chooses the ones it needs as it answers; the directory lists each by name.
Authorization
Fibery's own sign-in screen, reached after you type your workspace address, where you grant Claude its access. Given once per person.
Approval
The confirmation Claude waits for in the conversation before going ahead with something that would alter your workspace.
MCP
The common standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Fibery.
Connect

Plug Fibery into Claude in three steps

  1. 01

    Find Fibery in Claude

    In Claude's settings, open Customize, then Connectors, and look for Fibery. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first; after that, each member signs in on their own.

  2. 02

    Start the connection

    Click Connect on the Fibery row. Fibery asks for your workspace address, then opens its own sign-in window. If the link breaks later, use Disconnect and connect again from the same list.

  3. 03

    Read the authorization screen

    Look at Fibery's authorization screen before you accept. It belongs to Fibery, not to Claude, and it decides what the access covers. You can take that access back later from Fibery as well.

Tools

The 88 tools, sorted by what they do

Fibery gives Claude 88 tools: 29 that read your account, 59 that change something in it.

Two groups: what Claude reads and what it writes. Fibery documents every tool on the sheet, so there is no undocumented group here. Names stay as Claude shows them.

  • 29 read
  • 59 write

What Claude reads (29)

29 tools

Twenty-nine tools that explore the schema, query records, read documents, reports and automations, or check permissions.

display_automations_schema

Shows which actions and arguments are available for a given database and automation type, the menu Claude checks before it builds or adjusts a rule.

When it helps
before setting up a rule, Claude verifies that "add comment" is an available action for the Bugs database.

Sourcethe.fibery.io · September 30, 2026 ↗

display_entity_capabilities_via_sharing

Reports per-record access that comes from sharing: direct shares, access templates and assignment rules based on People fields, so you see who reaches a record and why.

When it helps
a manager wonders why a contractor can see one specific feature and not the rest of the roadmap.

Sourcethe.fibery.io · September 30, 2026 ↗

display_report_schema

Gives the report source schema for one or more databases, in other words what a report is able to draw from and which fields it can use.

When it helps
Claude checks which fields of the Bugs database a report can chart before promising a new graph.

Sourcethe.fibery.io · September 30, 2026 ↗

display_schema_capabilities

Reports what the current user can and cannot do at the space and database level across the workspace, a map of your own permissions.

When it helps
you want to know upfront whether your account has the right to add fields in the Product space before asking Claude for anything structural.

Sourcethe.fibery.io · September 30, 2026 ↗

download_file

Fetches a file attachment and returns a signed download link, valid for about an hour, plus its metadata; small images and supported text files come back inline for Claude to inspect.

When it helps
reading a CSV attached to a customer record.
Watch out
Fibery lists PNG, JPEG, GIF, WebP, PDF, CSV, Markdown and plain text as readable content, up to 20 MB each.

Sourcethe.fibery.io · September 30, 2026 ↗

fetch_by_url

Takes a Fibery link to a record or a view and returns what sits behind it, rendered as readable text in the conversation.

When it helps
you paste a link to a feature from a Slack thread and ask Claude what state it is in and who owns it.

Sourcethe.fibery.io · September 30, 2026 ↗

fetch_view_data

Runs a saved view and returns the records it would display, with the view's own filters applied, so Claude sees exactly what the team sees.

When it helps
a sprint health report that starts from the team's current Sprint board rather than from a fresh query.

Sourcethe.fibery.io · September 30, 2026 ↗

get_app_accounts

Lists the external app accounts connected to the workspace, such as Slack or email, whose identifiers some automation actions require.

When it helps
an automation has to post in the right Slack workspace and Claude needs to know which connected account is the correct one.

Sourcethe.fibery.io · September 30, 2026 ↗

get_automation

Fetches one automation rule or button by its identifier, with its triggers, filters and actions spelled out, so Claude can explain what it really does.

When it helps
checking exactly what the "notify on urgent bug" rule does before anybody tweaks it.

Sourcethe.fibery.io · September 30, 2026 ↗

get_automations

Lists the automation rules or buttons of one database, with their triggers, filters, actions and the identifiers needed for any later adjustment.

When it helps
"Show me the automation rules for Bugs", asked by a new team lead who inherited the workspace.

Sourcethe.fibery.io · September 30, 2026 ↗

get_connectors_list

Lists the built-in import integrations Fibery offers, such as Trello, Notion, Jira or CSV, so Claude knows which migrations are native.

When it helps
a team leaving Trello wants to know whether Fibery imports its boards natively before planning the switch.

Sourcethe.fibery.io · September 30, 2026 ↗

get_custom_apps_list

Shows the custom apps present in the workspace, the small React apps embedded in Fibery views, so nobody builds the same widget twice.

When it helps
a new developer takes stock of existing apps before starting on a new one for the sales team.

Sourcethe.fibery.io · September 30, 2026 ↗

get_entity_mention

Builds a live reference to a record, ready to embed in document content through the document tools, so the mention keeps pointing at the right record.

When it helps
release notes that point to each shipped feature with a live mention readers can click.

Sourcethe.fibery.io · September 30, 2026 ↗

get_fibery_skill

Loads the full reference guide for one Fibery domain: query, documents, views, reports, automations, whiteboard or custom apps.

When it helps
before a complex report, Claude reads the reports guide first.
Watch out
it teaches Claude Fibery's syntax, it holds none of your data.

Sourcethe.fibery.io · September 30, 2026 ↗

get_files_meta

Lists the file attachments sitting on records, with their details, so Claude knows what is attached where without opening every record.

When it helps
checking which customer contracts are still missing their signed PDF before the end of the quarter.
Watch out
it lists files, it does not return their content.

Sourcethe.fibery.io · September 30, 2026 ↗

get_me

Returns the name, email and identifier of the person signed in, the context Claude needs whenever a request is about your own work.

When it helps
a stand-up recap: Claude first needs to know whose work to look at before reading the activity log.

Sourcethe.fibery.io · September 30, 2026 ↗

get_report

Fetches a report by its identifier, with its tabs, sources and configuration, so Claude understands how it is put together.

When it helps
understanding how the quarterly report is built before anyone adds a tab or swaps its sources.
Watch out
it describes the report, it does not run it.

Sourcethe.fibery.io · September 30, 2026 ↗

get_reports_list

Lists every report view in the workspace, with enough detail for Claude to pick the right one or notice that none exists yet.

When it helps
finding out whether a churn report already exists somewhere before asking Claude to build a new one.

Sourcethe.fibery.io · September 30, 2026 ↗

get_user_mention

Builds a user mention ready to embed in document content through the document tools, so a person is tagged properly rather than just named.

When it helps
a meeting note that tags each owner next to their action item so they see it in their notifications.

Sourcethe.fibery.io · September 30, 2026 ↗

query

Fetches records from any database with filtering, sorting, pagination and aggregation, including sub-queries such as each feature with its linked bugs. Fibery calls it the main read tool.

When it helps
"Show me all urgent bugs that aren't done yet", or who holds the most open bugs right now.

Sourcethe.fibery.io · September 30, 2026 ↗

query_views

Lists saved views, boards, timelines, grids or documents, together with their configuration, so Claude can reuse the team's own lenses on the data.

When it helps
Claude looks for the team's Sprint board before reading it for a health report.
Watch out
listing a view is not the same as running it.

Sourcethe.fibery.io · September 30, 2026 ↗

read_document

Reads a document as a flat list of addressable blocks with stable identifiers, plus any inline comment threads attached to them.

When it helps
Claude needs a spec's structure and the reviewers' remarks before it proposes anything.
Watch out
Fibery advises reading a document first, before any work on existing content.

Sourcethe.fibery.io · September 30, 2026 ↗

schema

Lists every space and database in the workspace. Fibery says Claude calls it first before almost anything else, to know what exists and where.

When it helps
the first step of nearly every request, from a quick count of bugs to a new report.

Sourcethe.fibery.io · September 30, 2026 ↗

schema_detailed

Zooms into one database and shows all its fields, their types and their possible values, such as every workflow state, which Claude needs to work accurately with that data.

When it helps
Claude checks which states count as done before counting open bugs.

Sourcethe.fibery.io · September 30, 2026 ↗

search_guide

Searches Fibery's official documentation to answer questions about how Fibery itself works, rather than about the data in your workspace.

When it helps
someone asks how formula fields handle dates and Claude checks Fibery's own guide before answering.
Watch out
it never looks at your records.

Sourcethe.fibery.io · September 30, 2026 ↗

search_history

Looks up the activity log, who did what and when, with filters on database, record, author, date range and action type. By default it covers the last 24 hours, up to 50 events per call and at most 100.

When it helps
"What did the team work on this week?"
Watch out
a single request cannot span more than 12 months.

Sourcethe.fibery.io · September 30, 2026 ↗

What Claude writes (59)

59 tools

Fifty-nine tools that add, change, move or delete records, documents, fields, views, reports and automations. No source describes a confirmation specific to them: the general rule below applies.

add_chart_tab

Approval: see the rule

Appends a chart tab to an existing Fibery report, so the numbers of a report also show up as a visual.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
a product lead wants the bug count per sprint drawn as bars inside the weekly report.

Sourcethe.fibery.io · September 30, 2026 ↗

add_collection_items

Approval: see the rule

Puts items into a collection field of an entity: assigning a person, attaching a tag or linking a related record.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
linking a customer request to the feature that answers it, so both records point at each other.
Watch out
it adds to the collection, it does not replace what is already there.

Sourcethe.fibery.io · September 30, 2026 ↗

add_comment

Approval: see the rule

Posts a comment on an entity, or a reply to an existing comment on the same entity.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
Claude leaves a note on a bug summarising what three customers reported about it.
Watch out
a reply must target a comment that belongs to the same entity.

Sourcethe.fibery.io · September 30, 2026 ↗

add_file_from_url

Approval: see the rule

Downloads a file from a web address and attaches it to an entity's file field.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
a designer shares a mockup link and wants it stored on the feature it belongs to.

Sourcethe.fibery.io · September 30, 2026 ↗

add_inline_comments

Approval: see the rule

Anchors comments to selected text inside a document, the same threads people see in the Fibery editor, several at once if needed.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
Claude reviews a spec and flags three unclear sentences right where they sit.
Watch out
each comment has to stay within a single block.

Sourcethe.fibery.io · September 30, 2026 ↗

add_metric_tab

Approval: see the rule

Adds a metric tab to a report, a single headline number instead of a table or chart.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
the support dashboard needs one big figure: open tickets older than a week.

Sourcethe.fibery.io · September 30, 2026 ↗

add_table_tab

Approval: see the rule

Adds a table tab to a report, for readers who prefer rows and columns to a chart.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
finance wants the same report as a table to copy into a spreadsheet.

Sourcethe.fibery.io · September 30, 2026 ↗

create_automation

Approval: see the rule

Sets up an automation rule or a button for a database; rules need at least one trigger, buttons run when someone clicks them.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
when a bug is created, add a comment asking the assignee to triage it.
Watch out
Fibery recommends loading the automations guide first.

Sourcethe.fibery.io · September 30, 2026 ↗

create_avatars_fields

Approval: see the rule

Switches on avatar images for the entities of a database.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
a People or Customers database looks easier to scan with faces or logos next to names.

Sourcethe.fibery.io · September 30, 2026 ↗

create_comments_fields

Approval: see the rule

Enables comments on the entities of a database, so people can discuss each record.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
a new Design space should let reviewers comment on each task.

Sourcethe.fibery.io · September 30, 2026 ↗

create_custom_app

Approval: see the rule

Scaffolds a new custom app, one of the small React apps embedded in Fibery views, from Fibery's starter template.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
a developer wants a tailored widget inside a Fibery view and needs the skeleton ready.

Sourcethe.fibery.io · September 30, 2026 ↗

create_custom_app_dev_token

Approval: see the rule

Issues a short-lived access token for developing a custom app locally.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
a developer is about to work on a custom app from their own machine.
Watch out
treat the token like a password, even if it expires quickly.

Sourcethe.fibery.io · September 30, 2026 ↗

create_databases

Approval: see the rule

Builds one or more databases inside a space, the containers that hold a kind of record such as bugs or features.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
setting up Tasks and Milestones for a new team space in one go.

Sourcethe.fibery.io · September 30, 2026 ↗

create_entities

Approval: see the rule

Adds one or more new records to a database: bugs, features, tasks, customer requests.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
"Create a bug: form fields lose their value when switching tabs."

Sourcethe.fibery.io · September 30, 2026 ↗

create_files_fields

Approval: see the rule

Adds a file attachment field to a database so records can carry documents.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
contracts need their signed PDF attached to each customer record.

Sourcethe.fibery.io · September 30, 2026 ↗

create_formula_field

Approval: see the rule

Creates a calculated field from a plain-English description; Fibery generates the formula itself.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
a "days since last update" field on every feature, without writing formula syntax.

Sourcethe.fibery.io · September 30, 2026 ↗

create_icon_fields

Approval: see the rule

Turns on emoji icons for the entities of a database, a small visual marker shown next to each record's name in lists and boards.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
a roadmap board is easier to read at a glance with an icon per initiative.

Sourcethe.fibery.io · September 30, 2026 ↗

create_multi_select_fields

Approval: see the rule

Adds a multi-choice, tag-style field to a database.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
features need a Platforms field where web and mobile can both be ticked.

Sourcethe.fibery.io · September 30, 2026 ↗

create_primitive_fields

Approval: see the rule

Adds simple fields to a database: text, number, date, date range, checkbox, URL, email, phone, location or rich-text document.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
adding a Figma link field and a due date to design tasks.

Sourcethe.fibery.io · September 30, 2026 ↗

create_relation_fields

Approval: see the rule

Links two databases with a relation field, choosing its cardinality such as one-to-many or many-to-many, so records on both sides can point at each other.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
connecting bugs to the customer requests that reported them.

Sourcethe.fibery.io · September 30, 2026 ↗

create_report

Approval: see the rule

Builds a new report with its data sources and a title.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
a sprint health report pulling from bugs and features.

Sourcethe.fibery.io · September 30, 2026 ↗

create_single_select_fields

Approval: see the rule

Adds a single-choice dropdown with coloured options to a database.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
a Severity field on bugs with Critical, High, Medium and Low.

Sourcethe.fibery.io · September 30, 2026 ↗

create_space

Approval: see the rule

Opens a new top-level space in the workspace.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
a new Design space with task tracking linked to features.
Watch out
a space alone is empty; databases and fields come next.

Sourcethe.fibery.io · September 30, 2026 ↗

create_view

Approval: see the rule

Produces a new view: grid, list, board, timeline, calendar, gantt, gallery, map, feed, embed, form, standalone document or whiteboard.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
a board of open bugs grouped by assignee for the stand-up.
Watch out
documents and whiteboards start empty.

Sourcethe.fibery.io · September 30, 2026 ↗

create_workflow_field

Approval: see the rule

Defines the workflow field of a database: its stages and whether each one counts as not started, started or finished.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
a new Requests database needs New, In Review and Done states.

Sourcethe.fibery.io · September 30, 2026 ↗

delete_automation

Approval: see the rule

Permanently deletes an automation rule or button.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
retiring a rule that kept pinging the wrong channel.
Watch out
Fibery points to editing instead when you only want to change a rule.

Sourcethe.fibery.io · September 30, 2026 ↗

delete_avatars_fields

Approval: see the rule

Turns avatar images back off for a database's entities.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
a database of internal tickets does not need pictures after all.

Sourcethe.fibery.io · September 30, 2026 ↗

delete_comments_fields

Approval: see the rule

Disables comments on the entities of a database, removing the discussion thread that sat on each record.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
an archive database where no more discussion should happen once a project is closed.

Sourcethe.fibery.io · September 30, 2026 ↗

delete_databases

Approval: see the rule

Removes databases from a space.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
cleaning up a trial database created during a workshop.
Watch out
Fibery does not say what happens to the records a deleted database held, so read the name before you approve.

Sourcethe.fibery.io · September 30, 2026 ↗

delete_document_blocks

Approval: see the rule

Deletes blocks from a document, each with everything nested under it.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
stripping an outdated section from a product spec.
Watch out
nested content disappears along with its parent block.

Sourcethe.fibery.io · September 30, 2026 ↗

delete_entities

Approval: see the rule

Permanently deletes records. Fibery states that it cannot be undone.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
removing duplicate customer requests after a merge.
Watch out
there is no way back; read the list before agreeing.

Sourcethe.fibery.io · September 30, 2026 ↗

delete_fields

Approval: see the rule

Removes one or several fields from a database, taking them out of every record of that database.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
dropping an obsolete Priority field after the team moved to Severity.

Sourcethe.fibery.io · September 30, 2026 ↗

delete_icon_fields

Approval: see the rule

Switches emoji icons off for a database, so its records show their names without the small marker.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
a clean table view for a finance database where icons only add noise to the columns.

Sourcethe.fibery.io · September 30, 2026 ↗

delete_space

Approval: see the rule

Removes a whole top-level space.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
closing a temporary space once a project wraps up.
Watch out
the reference gives no detail on what a removed space takes with it, so check which one is named before you approve.

Sourcethe.fibery.io · September 30, 2026 ↗

delete_views

Approval: see the rule

Clears one or several views out of the workspace, while the records they displayed stay exactly where they were.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
tidying a space littered with abandoned boards and half-finished timelines after a reorganisation.

Sourcethe.fibery.io · September 30, 2026 ↗

delete_workflow_field

Approval: see the rule

Deletes the workflow field of a database together with the stages it defined for each record.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
a reference database that never needed states and only confuses people with a useless status column.

Sourcethe.fibery.io · September 30, 2026 ↗

execute_whiteboard_commands

Approval: see the rule

Creates, updates or deletes whiteboard elements: shapes, text, links, sticky notes, sections and freehand strokes.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
a retrospective board with Went well, Improve and Actions sections.
Watch out
Fibery recommends loading the whiteboard guide before editing.

Sourcethe.fibery.io · September 30, 2026 ↗

insert_document_blocks

Approval: see the rule

Inserts new blocks from Markdown, such as headings, paragraphs, lists, tables or images, before or after a block or at either end of the document.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
a structured bug description with Summary, Steps and Expected versus Actual.

Sourcethe.fibery.io · September 30, 2026 ↗

move_document_blocks

Approval: see the rule

Moves blocks, with all their children, to a new position in the document.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
bringing the Decisions section of a meeting note to the top.

Sourcethe.fibery.io · September 30, 2026 ↗

remove_collection_items

Approval: see the rule

Takes items out of a collection field: unassigning a person, dropping a tag, unlinking a record.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
a feature no longer depends on a retired component.

Sourcethe.fibery.io · September 30, 2026 ↗

remove_dimension

Approval: see the rule

Removes a dimension within a report tab, for example the breakdown that splits a chart by team or by month.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
a chart split by team becomes one global line for the executive summary.

Sourcethe.fibery.io · September 30, 2026 ↗

remove_tab

Approval: see the rule

Deletes a tab from a report, whether it held a chart, a metric or a table.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
an outdated metric tab confuses readers of the monthly report and should go.
Watch out
the report's other tabs stay as they are.

Sourcethe.fibery.io · September 30, 2026 ↗

rename_databases

Approval: see the rule

Renames databases, and can also move one to a different space.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
Requests becomes Customer Requests and moves to the Product space.

Sourcethe.fibery.io · September 30, 2026 ↗

rename_fields

Approval: see the rule

Gives one or several fields of a database a new name, without touching the values they hold.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
Owner becomes Product Owner to match the vocabulary the team actually uses in meetings.

Sourcethe.fibery.io · September 30, 2026 ↗

replace_block_text

Approval: see the rule

Swaps one exact text occurrence inside a block and leaves the rest untouched, so formatting and comments survive; Fibery calls it the preferred tool for small fixes.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
correcting a product name misspelt once in a long spec.

Sourcethe.fibery.io · September 30, 2026 ↗

reply_document_comment

Approval: see the rule

Adds replies to existing inline comment threads, several in one call if needed.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
Claude answers reviewer questions left on a draft.

Sourcethe.fibery.io · September 30, 2026 ↗

set_block_attrs

Approval: see the rule

Changes block attributes: heading level, task done or to-do state, code language, callout icon.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
ticking off the checklist items of a launch plan that are complete.

Sourcethe.fibery.io · September 30, 2026 ↗

set_block_text

Approval: see the rule

Rewrites the inline content of one or more existing text blocks from Markdown, keeping each block's type, attributes, identifier and position.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
tightening the wording of every paragraph in an introduction.

Sourcethe.fibery.io · September 30, 2026 ↗

set_state

Approval: see the rule

Moves a record to another workflow state, for example from In Progress to Done, the way someone would drag a card across a board.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
"Move all Implemented features to Done" at the end of a release.

Sourcethe.fibery.io · September 30, 2026 ↗

update_automation

Approval: see the rule

Modifies an existing rule or button: rename it, enable or disable it, replace triggers or filters, and add, change or delete actions.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
pausing a rule during a migration.
Watch out
Fibery advises fetching the automation and its action identifiers first.

Sourcethe.fibery.io · September 30, 2026 ↗

update_dimension

Approval: see the rule

Adjusts a dimension within a report tab, such as the field a chart is grouped by.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
grouping a velocity chart by month instead of by week for the quarterly review.

Sourcethe.fibery.io · September 30, 2026 ↗

update_entities

Approval: see the rule

Updates fields on existing records; only the fields you name are changed.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
marking a bug as urgent and setting its due date in one go.

Sourcethe.fibery.io · September 30, 2026 ↗

update_formula_field

Approval: see the rule

Updates a calculated field, again from a plain-English description that Fibery turns into the formula.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
a prioritisation score should now weigh customer demand twice as much as effort.

Sourcethe.fibery.io · September 30, 2026 ↗

update_multi_select_fields

Approval: see the rule

Modifies a multi-choice field and its options, such as adding, renaming or recolouring a choice.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
adding Tablet to the Platforms options now that the app ships on iPad.

Sourcethe.fibery.io · September 30, 2026 ↗

update_report

Approval: see the rule

Updates a report's title and/or its data sources, leaving its tabs in place.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
the quarterly report should now include the Requests database alongside Bugs and Features.

Sourcethe.fibery.io · September 30, 2026 ↗

update_single_select_fields

Approval: see the rule

Edits a single-choice dropdown and its coloured options, for example a label or a colour.

What Claude asks for
Fibery's reference says nothing about a confirmation here, so the general approval rule is what applies.
When it helps
renaming the Medium severity to Normal after a vocabulary review with the support team.

Sourcethe.fibery.io · September 30, 2026 ↗

update_tab

Approval: see the rule

Adjusts scalar properties of a report tab, such as its name or simple display settings.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
renaming a tab from "Chart 2" to something readers understand at a glance.

Sourcethe.fibery.io · September 30, 2026 ↗

update_view

Approval: see the rule

Edits an existing view's name, description, space or configuration.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule applies.
When it helps
narrowing a board to the current quarter.
Watch out
a supplied configuration replaces the previous one entirely.

Sourcethe.fibery.io · September 30, 2026 ↗

update_workflow_field

Approval: see the rule

Reshapes the workflow field of a database: its stages and whether each counts as not started, started or finished.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
adding a Blocked stage between In Progress and Done for the engineering team.

Sourcethe.fibery.io · September 30, 2026 ↗

Approvals

What Claude asks before acting

By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request appears in the conversation when it matters.

On a Team or Enterprise workspace, owners decide whether members may let some actions through without a prompt each time. They can also restrict what a connector may do across the organization, keeping queries open and closing every write, and nobody overrides that from a personal account. Claude works with the Fibery rights of the connected person and nothing more: two tools even report those rights, at space and database level and record by record through sharing. With 59 write tools, including permanent deletions, the default approval is worth keeping.

Plans

Which plans include it

Of the 819 sheets in the official directory, none shows availability per plan. That connector-by-connector answer is published nowhere: a real gap in the catalogue.

The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before members can sign in. What your Fibery subscription includes is a separate matter, set by Fibery. For the up-to-date state of this connector, check its sheet in the official directory.

Limits

Where the Claude Fibery connector stops

A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a record changes state or a comment is posted.

Only Fibery documents this connector: no Claude help article covers it, so these limits come from Fibery's user guide, its tool reference and the directory sheet. The tool list is an observed floor, not a promise, since administrators can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic states on each sheet that it neither picks a publisher's tools nor guarantees how they behave. For a connector whose sources disagree on what it may send, compare with the Claude gmail connector.

Need help

Need help connecting Fibery to Claude?

A person reads every message.

FAQ

Questions about the Claude Fibery connector

01What can Claude do with the Fibery connector?
Claude can do most of what you do in Fibery yourself, according to Fibery. Its 29 read tools explore spaces, databases and fields, query records with filters and aggregation, run full-text search, read documents, views, reports and automations, and look up activity history. Its 59 write tools create, update and delete records, move them through workflow states, edit documents and comments, attach files, add fields and databases, build views, reports and whiteboards, and set up automation rules.
02Can Claude delete records or change the structure of my Fibery workspace?
Yes. Claude can delete records, spaces, databases, fields, views, document blocks and automations, and it can reshape the schema by adding databases and fields of any type, formulas included. Fibery states that deleting records is permanent and cannot be undone, and that deleting an automation is permanent too. If that level of access worries you, owners on Team and Enterprise can block write tools for the whole organization while keeping queries open.
03Does Claude ask before changing my Fibery workspace?
No source describes a confirmation specific to the Fibery tools, so the general rule applies: by default, Claude asks for your approval before each action it takes on an account on your behalf. On Team and Enterprise workspaces, owners decide whether members may let some actions run without a prompt each time. Given that some deletions cannot be reversed, keeping that default in place for write actions is a sensible habit.
04Which Claude plans include the Fibery connector?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and that on Team and Enterprise an Owner or Primary Owner must turn the connector on for the organization first. What your Fibery subscription covers is a separate question. For the current state, open the connector's sheet in the official directory from your account.
05Does Claude see everything in my Fibery workspace?
Claude sees what the connected person can see, and nothing more. Two tools make that explicit: one reports what the current user can and cannot do at space and database level, the other lists which records are reachable through sharing, access templates and assignment rules. If a space is closed to you in Fibery, it stays closed in the conversation too. To cut access, disconnect the connector in Claude or revoke it from Fibery.
06How far back can Claude look in Fibery's activity history?
By default, the history tool covers the last 24 hours and returns up to 50 events per call, with a maximum of 100. A single request cannot span more than 12 months. Within that window, Claude can filter the log by database, record, author, date range, action type and schema changes, which is exactly how a weekly recap or release notes get built from what actually happened in the workspace.
07Claude or an automation tool for Fibery: which fits which job?
They do different jobs. Claude with this connector suits work you steer in a conversation: a sprint report, a triage pass on customer requests, a new space set up from a description. Automation fits what must happen without anyone asking, such as reacting every time a record changes. Fibery has its own automation rules, which Claude can even set up for you, and external tools cover cross-app flows. The connector itself never starts on its own.