
Connectors / Operations · HTTP Connector
Automate Fibery with Tray.ai
Create an entity, upload a file and create a database in Fibery, and start a workflow when Fibery sends “Entity changed”.
What can you do with Fibery on Tray.ai?
Fibery is a connected workspace where teams build their own databases for product management, projects, CRM and knowledge, linking records across them. Tray.ai connects to Fibery through the HTTP Connector, so your workflows can call the Fibery API alongside the rest of your stack.
- When Fibery sends “Entity changed”, update the matching record in your CRM.
- Create an entity for each feature request your support team logs in your help desk.
- Attach a file to an entity when a signed contract lands in your document storage.
- Connects through
- HTTP Connector
- Authentication
- An API key in a request header
- Base URL
- https://{account}.fibery.io/api
Set it up
Connect Fibery to Tray.ai
Each step uses Fibery's own API details, from its documentation.
Step 1
Save Fibery's API key
Save the key as a Tray.ai authentication. The HTTP Client puts it in the request header, read from $.auth. The key stays out of the workflow and out of the logs.
Step 2
Point the HTTP Client at the API
Add an HTTP Client step and use https://{account}.fibery.io/api as the base URL. Or paste a cURL example from Fibery's API docs, and Tray.ai fills in the method, URL, and headers.
Step 3
Start with “Query entities”
It's one of 11 documented actions, under Entities. The response comes back as data the next step can map into your other apps.
Step 4
Start workflows from Fibery events
Give Fibery the URL of a Tray.ai webhook trigger. “Entity changed” can then start a workflow.
Workflows to build with Fibery
Each one uses actions and events from Fibery's own API documentation.
Post Fibery record changes to Slack
When
Entity changed
Then
- Query entities for the changed record
- Post the change to the product channel in Slack
With Slack
Create Fibery entities from new Zendesk feature requests
When
A ticket is tagged as a feature request in Zendesk
Then
- Create an entity in the feedback database
- Attach a file to an entity with the ticket export
With Zendesk
Mirror Fibery changes back to Jira
When
Entity changed
Then
- Query entities
- Update the linked issue in Jira
With Jira
Apps you can build on Fibery data
Internal tools your team can build with an AI assistant, each one using Fibery calls from its API documentation.
Cross database tracker
Queries linked records across databases and lets a team update fields from one view.
Request intake form
Lets anyone submit a request with a file that lands as a new record in the right database.
Give your AI agents Fibery tools
Build an MCP server on Fibery in Agent Gateway and choose which actions your agents can call. Every call runs with access control and an audit trail. How Agent Gateway works
- Query entities
- Upload a file
- Create a database
- Create a webhook
- Create an entity
- Update an entity
- Delete an entity
- Attach a file to an entity
What the Fibery API covers
4 resources and 11 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.
Entities
- Query entities
- Create an entity
- Update an entity
- Delete an entity
Files
- Upload a file
- Attach a file to an entity
Schema
- Create a database
- Add a field
- Update the workspace schema
Webhooks
- Create a webhook
- Delete a webhook
Events Fibery can send to a Tray.ai webhook trigger
- Entity changed
Checked against Fibery's own documentation on 2026-10-22
How Tray.ai makes this work
Fibery plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 12,000+ apps, databases, APIs, and services with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in Fibery — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose Fibery actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Tray Helix
Build apps on Fibery data with your AI assistant, then deploy, run, and govern them on Tray.ai.
Learn more →More operations apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every operations connector →
Frequently asked questions
What can a Tray.ai workflow do in Fibery?
+
The Fibery API documents 11 actions across 4 resources (Entities, Files, Schema, Webhooks). For example: Query entities; Upload a file; Create a database. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with Fibery?
+
The Fibery API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.
Which Fibery events can start a Tray.ai workflow?
+
Fibery sends one event to a webhook URL, for example: Entity changed. A Tray.ai webhook trigger receives them and starts a workflow.
See Fibery working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.