Documentation
Connectors: GitHub, Slack, Notion, Linear and Tavily
Connectors link your account to the apps workflows work with. Each connection belongs to your account only, and its token never leaves the server: workflows ask Worfilo to run an action, and never see the token itself.
Available apps
- GitHub: create issues, comment on issues, list issues, and read a repository.
- Slack: post a message and list channels.
- Notion: search, create a page in a database, and append text to a page.
- Linear: create an issue in a team and search issues.
- Tavily: web search and page extraction built for AI agents.
Connect an app
Open Connectors in the sidebar and choose an app. Where the server is set up for it, choose Continue with the app and approve access in its own window. You can always paste a token instead, such as a GitHub fine-grained token, a Slack bot token, a Notion integration secret, a Linear API key, or a Tavily API key.
Use it in a workflow
In the editor palette, Connected apps lists your connections. Adding one creates a Connector node with the connection chosen; pick an action and fill its inputs. Inputs accept templates, so a value can come from the trigger or an upstream node:
Owner: octocat
Repository: hello-world
Title: {{ nodes.classify.output.structured.summary }}Give it to an agent
Connect a Connector node to an Agent's tools port with a tool edge. The agent sees the action's inputs as the tool's arguments and fills any you left empty; the ones you filled in stay fixed, so an agent can search with Tavily or open GitHub issues only where you allow it.
When a connection stops working
If an app revokes access or a token expires and cannot be refreshed, the connection is marked Needs reconnecting. Runs that use it fail with a message that says so, and validation flags the node before you run. Disconnect it and connect the app again.
Keep reading
- Connector node: run an action on a connected appThe Connector node runs a GitHub, Slack, Notion, Linear or Tavily action with your account's connection, as a workflow step or as a tool an agent can call.
- Custom APIs: connect any HTTP API with any authRegister any HTTP API once with its base URL and auth, from no auth and API keys to OAuth 2.0 and AWS Signature v4, then call it from workflows and agents.
- MCP servers: a marketplace of tools for your workflowsConnect a Model Context Protocol server from the marketplace or by URL, and call its tools from a workflow node or hand them to an agent.
Build it on the canvas
Create a free account, describe the workflow or wire it yourself, and run it in the browser.