Skip to main content
A tool node calls one of Fibonacci’s built-in integrations. This page lists all of them, as the platform runs them today. GET /api/v1/tools (or list_tools() in the SDK) returns the same catalog with full JSON schemas.

Using a tool node

Passing data between steps

Templates work anywhere in tool_params, including inside lists and objects: "attendees": ["{{input.email}}"].
Tool outputs are objects. Pick the field you need ({{create_channel.channel_id}}): passing {{create_channel}} hands the whole JSON to a tool that expects an ID.

Credentials

Tools that talk to a service read their credentials from the Secrets Locker of the person running the workflow (or from your organization’s connection, for Slack). See Connect your tools. A tool whose credentials are missing fails with a message that names the secret to add; nothing else in the workflow is affected unless a later step needs its output.

Side effects

Every tool declares what it does to the world, and governance keys off that, never off the tool’s name:
  • read: only fetches data
  • write: changes something inside a connected system (a ticket, a card, a page, a channel)
  • egress: delivers content to people or places outside the run (a message, an email, an invitation, a comment)

Developer tools

Full guide: Developer workflows.

GitHub

Needs GITHUB_TOKEN. Repositories can be owner/name, a link or just the name; issues and pull requests 23, #23, owner/name#23 or a link.

Jira (Cloud)

Needs JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN. Issues are a key (OPS-7) or a link. Descriptions and comments are Markdown. Your Jira credentials only ever go to JIRA_BASE_URL, over HTTPS: a link to another Jira site is refused, not followed. assignee takes me, an email or a display name; status moves the issue through the transition that leads there.

Trello

Needs TRELLO_API_KEY, TRELLO_TOKEN. Boards by name, link or ID; lists by name; cards by link, ID, or by name together with board.

Google Workspace

Sign in with Google (Settings → Integrations); runs use your Google login.
  • gmail_send with to: "me" sends to whoever ran the workflow. attachment_name + attachment_content attach a text file, such as a generated fix.md.
  • google_calendar_create_event without start_time books the next business day at 10:00 in your calendar’s time zone; without end_time, it lasts duration_minutes (30). add_meet_link: true adds Google Meet. Attendees get Google’s invitation email.
  • Google Sheets and Docs IDs can be pasted as full links in governance rules.

Messaging

Slack

An org admin can connect the workspace once (Organization → Integrations → Add to Slack); runs in that org then post as the Fibonacci bot. Otherwise a member’s SLACK_BOT_TOKEN is used.
  • channel: "@me" (or a person’s email) is a direct message, which is what reaches a phone.
  • slack_create_channel invites the person who ran the workflow, plus anyone in invite (emails or member IDs). Someone who can’t be invited shows as a warning in the run log; the channel is still created.
  • Errors such as channel_not_found name the workspace the bot is in and how to /invite it.

Discord

Needs DISCORD_BOT_TOKEN and DISCORD_GUILD_ID (and DISCORD_USER_ID for @me). Setup: Organization → Integrations → Discord. Channels go under one “Fibonacci” category and are reused if they exist. Long messages are split at 2,000 characters, and mentions never ping.

Notion and Zoom

notion_create_page returns page_id and url; zoom_create_meeting returns meeting_id, join_url and start_url.

Built in (no credentials)

Files you attach when you run a workflow (PDF, Word, Excel, CSV) don’t need a tool: their text reaches LLM steps as {{input.uploaded_files}}.

Discovering tools


Timeouts and retries

  • Each call gets the node’s config.timeout, or the tool’s default: 30 seconds, and 90 for web_search.
  • A failed call is retried up to config.max_retries (3) times with a growing delay, unless retrying can’t help: a bad or missing credential, a missing permission, something that doesn’t exist, or an input that isn’t valid. Those fail once, with a message that says what to change.
  • Mark steps whose failure shouldn’t stop the run with "config": {"continue_on_error": true}, typically notifications:

Next steps

Developer workflows

GitHub, Jira and Trello, end to end

Governance

Rules, approvals and receipts for every tool call