Croft connectors: Xero, Stripe, Slack, Linear and more for your AI-built apps

Croft launched a catalogue of connectors that let apps built with AI assistants call outside tools such as Xero, Stripe, Slack, Linear, Brevo and Jotform without storing credentials in the app's code, the company said in an October 26, 2026 blog post by Rich Chetwynd. Croft stores each credential encrypted and routes app requests through its gateway, which checks the app is allowed, adds the key on the way out and returns only the result, so one connection can serve many apps. Some connectors, including Xero and Google Search Console, are also kept in sync as a curated copy of the data on the customer's own server for AI queries.

Blog https://oncroft.net/blog/ · October 26, 2026 · Rich Chetwynd Croft connectors: Xero, Stripe, Slack, Linear and more for your AI-built apps A guide to Croft connectors for AI-built apps: how they work, which finance, email, forms, scheduling and project tools you can connect, and how Croft holds the credentials so your apps never do. Quick answer A Croft connector lets the apps you build with an AI assistant use an outside tool, such as Xero, Stripe, Slack, Linear, Brevo or Jotform, without the credential ever sitting in the app’s code. You paste a key or sign in once. Croft https://oncroft.net/ keeps the credential encrypted, and your apps call the tool through Croft’s gateway. The full catalogue is on the connectors page https://oncroft.net/connectors/ ; this guide explains how connectors work and which ones fit which job. How Croft connectors work When an AI assistant builds an app that needs an outside service, the easy path is to paste the API key into the code. That works until the app is shared, copied or leaked, and then the key goes with it. Croft does it differently: 1. You connect the tool once. Sign in or paste your own key in Croft. You can ask your assistant to do it, for example “connect our Stripe account.” 2. Croft holds the credential. It is stored encrypted and never shown to an app or written into generated code. 3. Apps ask through a gateway. An app does not call the tool directly. It asks Croft, which checks the app is allowed, adds the key on the way out and hands back only the result. 4. One connection, many apps. Every app you allow can use the same connector. Change the key in one place and everything keeps working. Some connectors, such as Xero https://oncroft.net/connectors/xero/ and Google Search Console https://oncroft.net/connectors/googlesearchconsole/ , are also kept in sync : Croft keeps a curated copy of the data on your own server so your AI can query it. How synced data works https://oncroft.net/data/ covers that side. The rest of this guide is about the apps you build. You bring your own AI assistant and your own accounts with each tool. Croft holds the connection, not the subscription. Finance and accounting Finance is where leaking a key hurts most, so it is the clearest case for keeping credentials out of app code. - Xero https://oncroft.net/connectors/xero/ : read invoices, reconcile payments and pull accounting data into reporting tools. Typical apps are a month-end close checklist, or a view of overdue supplier invoices for people who should not have a full Xero login. If you mainly want to ask questions about your books, see how to ask Claude about your Xero data https://oncroft.net/blog/ask-claude-about-your-xero-data/ , or use Xero data in a private internal app https://oncroft.net/blog/use-xero-data-in-private-internal-apps/ . - Stripe https://oncroft.net/connectors/stripe/ : payments and subscriptions. Examples include a refund approval app where support requests and finance approves, or a subscription health dashboard. Read more in how to connect an AI app to Stripe https://oncroft.net/blog/how-to-connect-an-ai-app-to-stripe/ . - Square https://oncroft.net/connectors/square/ and Paddle https://oncroft.net/connectors/paddle/ cover point-of-sale and subscription billing in the same way. Email and messaging Most internal apps end up needing to tell someone something. The email connectors let an app send mail without carrying a sending key: - SendGrid https://oncroft.net/connectors/sendgrid/ , Postmark https://oncroft.net/connectors/postmark/ , Mailgun https://oncroft.net/connectors/mailgun/ and Resend https://oncroft.net/connectors/resend/ for transactional email such as approval requests, receipts and weekly reports. - Brevo https://oncroft.net/connectors/brevo/ for email plus contact and list management, for example adding a contact to a sequence when a demo request form comes in. - Loops https://oncroft.net/connectors/loops/ , ConvertKit https://oncroft.net/connectors/convertkit/ and beehiiv https://oncroft.net/connectors/beehiiv/ for lifecycle email and newsletters. - Slack https://oncroft.net/connectors/slack/ for posting messages and reading channels. A common pattern is an approval app that posts a request to a channel and updates the thread when someone decides. If you are picking one, the apps work the same way from your side. Choose the provider you already pay for. The step-by-step version for email is in how to send email from an AI-built app https://oncroft.net/blog/how-to-send-email-from-an-ai-built-app/ . Forms, scheduling and project tools Many small teams already collect work in forms and calendars and track it in a project tool. Connectors let a Croft app sit on top of those: - Forms: Jotform https://oncroft.net/connectors/jotform/ , Typeform https://oncroft.net/connectors/typeform/ and Tally https://oncroft.net/connectors/tally/ let an app read submissions, for example to route a signed contract to the right reviewer or triage inbound leads. - Scheduling: Cal.com https://oncroft.net/connectors/caldotcom/ and Calendly https://oncroft.net/connectors/calendly/ give apps access to bookings, for example a meeting prep view or a no-show tracker. - Project and task tools: Linear https://oncroft.net/connectors/linear/ , Asana https://oncroft.net/connectors/asana/ , ClickUp https://oncroft.net/connectors/clickup/ , Monday.com https://oncroft.net/connectors/mondaydotcom/ and Todoist https://oncroft.net/connectors/todoist/ . A sprint health dashboard or a roadmap status page for stakeholders is a typical Linear app. - Docs and data: Notion https://oncroft.net/connectors/notion/ , Coda https://oncroft.net/connectors/coda/ and Airtable https://oncroft.net/connectors/airtable/ work as a source or destination for an app’s data. If you are starting from a spreadsheet, see how to turn a Google Sheet into an app https://oncroft.net/blog/how-to-turn-a-google-sheet-into-an-app/ . There are also connectors for CRM HubSpot https://oncroft.net/connectors/hubspot/ , Pipedrive https://oncroft.net/connectors/pipedrive/ , Attio https://oncroft.net/connectors/attio/ , GitHub https://oncroft.net/connectors/github/ , and AI model providers such as OpenAI https://oncroft.net/connectors/openai/ and Anthropic https://oncroft.net/connectors/anthropic/ , so an app can call a model without a model key in its code. Credentials and admin governance Holding the key is the first half. The second half is deciding who gets to use it. - The key stays with Croft. It is encrypted, never shown to an app, and not written into the code your assistant generates. A leaky app cannot spill a key it never had. - Sensitive connectors can need approval. Mark a connector, such as payroll or your customer database, as needing an admin’s approval. Anyone can build an app that asks to use it, but it stays off until an admin says yes. - Approve narrowly. Approve a connector for a specific app or person, not the whole company. - There is a record. Connectors, approvals and use are logged, so “who can reach our billing data?” has an answer. Roles still apply on top. See roles and permissions https://oncroft.net/docs/roles-and-permissions/ and the security overview https://oncroft.net/security/ . For the technical detail, including how requests are made, read the connectors docs https://oncroft.net/docs/connectors/ . Request a connector If the tool you need is not in the catalogue, you have two options: - Use the custom connector. It lets apps call any HTTP API through Croft’s gateway. You set the base URL and auth method once and the credentials stay with Croft. This is how you would reach an internal system, a niche SaaS tool or a legacy API. See the custom connector https://oncroft.net/connectors/custom/ . - Ask for a dedicated one. Email \ email protected\ https://oncroft.net/cdn-cgi/l/email-protection 2551404448654a4b46574a43510b4b4051 with the tool’s name and what you want to build. Please do not send keys or passwords. More on support https://oncroft.net/support/ . FAQ What is a connector on Croft? A connector lets an app use an outside tool such as Xero, Stripe, Slack or Linear, with the credential held by Croft and never written into the app’s code. Does my AI-built app hold my API keys? No. The app asks Croft to make the call. Croft checks the app is allowed, adds the key on the way out and returns the result. Can I connect a tool that is not in the list? Yes, with the custom connector https://oncroft.net/connectors/custom/ , or by emailing us to request a dedicated one. Can I restrict who can use a connector? Yes. Sensitive connectors can require an admin’s approval for a specific app or person, and use is logged. Do I need my own account with each tool? Yes. You sign in or paste your own key for each tool, and Croft holds it. See pricing https://oncroft.net/pricing/ for current Croft plans. Browse all connectors → https://oncroft.net/connectors/ · Start free trial → https://app.oncroft.net/signup · Connectors docs → https://oncroft.net/docs/connectors/ Start your free trial. Your team's first app could be live before lunch. No card. 7 days. Cancel anytime.