Custom connector for Croft: any API in your internal apps
Connect any API to Croft with a custom connector so internal apps can use services not in the built-in catalog - with your credentials held by Croft, never in code.
How it works
The custom connector lets apps on Croft call any HTTP API through Croft's gateway. Your API keys, OAuth tokens, or basic auth credentials stay encrypted with Croft; apps make requests without holding secrets. One custom connector can be shared across allowed apps, so your team can integrate internal systems, niche SaaS tools, or legacy APIs without scattering credentials through generated code. You configure the base URL, auth method, and headers once; apps call endpoints by path.
Use cases
What you can build
Build a warehouse inventory app that reads stock levels from your legacy ERP system's REST API without exposing database credentials.
Create a compliance dashboard that pulls audit logs from your internal security tool's API and flags anomalies for review.
Let your finance team sync invoice data from a niche accounting platform that does not have a dedicated Croft connector yet.
Connect this tool to Croft
Your API credentials stay encrypted with Croft and never appear in app code. Apps call the connector through Croft's gateway, which checks permissions and adds the key on the way out. One connection can be shared across multiple apps you allow, with a full audit trail of every call.
Stake out your croft.
Your team's first app could be live before lunch.
Get your croft7 days free, no card to start. From $24/month - cancel anytime and take everything with you.