Connectors
Plug your apps into the tools you already use.
A connector lets the apps you build tap into your other tools — your CRM, your payment provider, your email — so an app can use that data without you copying it around. You add each tool's key to Croft once; it's kept locked away, and your apps use the connection without the key ever touching their code.
Bring your whole stack
Connect the tools you already run on.
Pick a tool and paste your own key — nothing to set up on their side. Your assistant can wire it in for you, or add a custom connector for any other API.
30+ tools and counting — plus a custom connector for anything with an API.
Built the safe way
Your keys never go near your apps.
The key stays with Croft
You paste a tool's key once, and Croft keeps it encrypted and out of sight. It's never shown to an app and never written into the code your assistant generates — so there's no secret sitting in a file waiting to leak.
Apps ask through a gate
An app doesn't hold the key — it asks Croft to make the call. Croft checks the app is allowed, adds the key on the way out, and hands back only the result. A leaky app can't spill a key it never had.
One source, shared safely
Connect a tool once and every app you allow can use it — no re-entering keys, no copies of your customer list scattered across apps. Change the key in one place and everything keeps working.
Apps reach your tools only through Croft, which holds the keys and checks every request — the same least-privilege pattern security teams rely on.
For teams
Shared where it helps. Locked where it matters.
Not every data source should be open to everyone. Croft lets you keep the everyday tools flowing while putting a gate in front of the sensitive ones.
Sensitive sources need a nod
Mark a connector — say payroll or your customer database — as needing approval. Anyone can build an app that asks to use it, but it stays switched off until an admin says yes.
Only the right people, the right apps
Approve a connector for a specific app or a specific person — not the whole company. New starters and one-off tools don't get the keys to everything by default.
A record of who connected what
Every connector, approval, and use is logged. If someone asks "who can reach our billing data?", the answer is a page, not a guess.
Roles decide who can do what — see roles & permissions
The short version
Your data, connected — on your terms.
Connectors let the apps you build lean on the tools you already trust, without scattering keys through your code or handing every employee the run of the place. Shared data where it helps the work, a gate where it protects the business — set up by asking your assistant, kept safe by Croft. The technical detail →
FAQ
Frequently asked questions
What is a connector on Croft?
A connector lets your apps use an outside tool — Stripe, a CRM, email, any API — with the key held by Croft and never written into an app’s code. You set one up by asking your assistant, for example “connect our Stripe account.”
Which tools can I connect?
Popular tools like Stripe, HubSpot, Slack, GitHub, Airtable, Notion, and 45+ more, plus a custom connector for any other API.
How does Croft keep connector keys secure?
Apps never hold the key. They call the connector through Croft’s gateway, which checks the app is allowed and adds the key on the way out — so a leaky app can’t spill a key it never had. Keys are encrypted and never shown to apps.
Can I control who can use a data source?
Yes. A sensitive connector, such as payroll or a customer database, can require an admin’s approval before a specific app or person is allowed to use it, with a full audit trail of who connected what.
Can two apps share the same data?
Yes. Connect a data source once and every app you allow can use it, so you’re not copying your customer list into every app or re-entering keys.
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.