Native integrations cover billing and issue trackers. Everything else (seats, workspaces, feature flags, logs) can still sit next to the conversation. Point Fernand at an HTTP endpoint you already have.
Included in our $29/human/month transparent pricing
Custom data is how Fernand stays small on native integrations without leaving you stuck. If the thing you need to see is in your own admin API, Fernand can fetch it when a conversation opens and render it in the sidebar.
You connect an endpoint, add headers such as an authorization token, and describe the display with HTML and Liquid. Conditions and loops are supported, so the sidebar can change based on plan, status, or a list of resources. You do not have to learn a private widget format.
It is not display-only. Interactive forms in the sidebar can send data back to your endpoint, with validation, predefined headers, and the HTTP method you choose. That is how a support reply and an account change happen in the same place.
Fernand calls the URL you configure when it needs customer context. Add one or more headers for auth. Use the endpoint you already have for your admin UI when you can.
Display data with HTML and Liquid, including conditions and for-each loops. You control what shows up, not a rigid field mapper.
Text, lists, buttons, key/value pairs, badges, pills, cards, dividers, spacers, tables, tabs, collapsibles, and forms. Built so the extra data does not steal attention from the reply.
Collect input in the conversation, update a customer in your system, or trigger an action through your API. Methods, headers, and validation are part of the form, not a side script.
The Fernand API can read custom data API logs, which is what you want when the sidebar is empty and you need to know whether your endpoint returned 200.
Your billing provider does not know how many projects the customer created this week. Your API does. Put that in the sidebar so you are not asking them to paste a screenshot of their dashboard.
Render a button to your own dashboard, scoped to that customer. One click, no searching.
A small form posts to your endpoint and updates the account. You still write the human reply in Fernand.
Keep Stripe for plan and invoices. Use custom data for the product-specific objects Stripe will never know about.
Fernand calls your endpoint with the contact context, then renders the template in the sidebar of the shared inbox.
Fernand AI and your own eyes can both see what the endpoint returned. Fewer “can you remind me which workspace?” emails.
Use a form in the sidebar, or a webhook from a rule or snippet, or the Fernand API from a coding agent. Custom data is the pull. The API is the rest.
A coding agent can help write the Liquid template. The Fernand setup prompt walks through custom data after the inbox is connected.
Straight answers, without the marketplace filler.