Integrations
Your app is only useful once it talks to everything else.
Databases, sign-in, payments, email and models are already wired into the platform. Ask for the one you need and it is connected — with the keys kept on the server, where they belong.
An integration looks small on paper. An API key, a couple of endpoints, a response to read. The work is everything around it: where the key lives, what happens when the call fails, who is allowed to trigger it, and how you find out when the provider quietly changes something.
That layer comes with the platform. You describe what should happen, and the connection, the retries and the secrets are handled for you.
What you can connect
The common ones are already here. The rest is a conversation away.
Databases and files
Your own tables with real relationships, plus file uploads and object storage, all queried from the server.
Sign-in
Email and password, magic links, Google, Microsoft and Apple. SSO and directory sync on Enterprise.
Payments
Stripe and PayPal checkout, subscriptions and one-off charges — into your account, not ours.
Email and messaging
Transactional email, SMS and WhatsApp notifications sent from your own sender identity.
AI models
Text, image and speech models called from your app, with usage counted per account so nobody runs away with it.
Sheets and documents
Read and write Google Sheets, generate PDFs, and send a report on a schedule without anyone pressing a button.
Webhooks and automation
Receive webhooks from anywhere, send your own, or hand the rest to Zapier and Make.
Anything with an API
Point YeshBe at the documentation and it writes the client, the authentication and the error handling.
Keys and secrets
Your credentials never reach the browser.
Every integration runs server-side. Keys are stored encrypted and referenced by name, so a secret is never in the bundle, never in a repository and never sitting in someone's network tab.
- Separate credentials for your test and live environments.
- Rotate a key once and every call picks up the new one.
- Role rules decide who can trigger an integration at all.
When a provider misbehaves
Failed calls are expected, not a surprise.
Timeouts, rate limits and outages are handled by the platform instead of being left to a request nobody wrapped. Anything that keeps failing turns up in your logs alongside the call that caused it.
- Transient failures retried with backoff.
- A readable log of every outbound call and its response.
- An alert when an integration starts failing consistently.
What it costs
Integrations run on integration credits.
Every plan includes a monthly allowance, spent when your app calls an external service. Building and testing a connection costs nothing — credits go when the app is actually doing the work.
- Usage shown per integration, so you can see what is expensive.
- Set a ceiling per app so a loop cannot cost real money.
- Bring your own provider account and pay the provider directly.
Adding one
No SDK to install and no boilerplate to copy from a blog post.
Say what you need
"Email the customer a receipt when they pay." That is the whole specification.
Sign in to the provider
A guided connection screen for services that support it, or paste a key once.
Try it on test data
Run the flow against the provider's sandbox before a real customer sees it.
Publish
Live credentials swap in at publish time. Nothing else about the app changes.
Before you connect something
What if the service I use is not listed?
Point YeshBe at the provider's API documentation and it builds the client, including authentication and error handling. Anything with a documented HTTP API can be connected.
Where are my API keys kept?
Encrypted on the server and referenced by name. They are never included in the code sent to the browser, and people you invite into the workspace cannot read them unless you grant that permission.
Whose account are the external services billed to?
Yours. You connect your own Stripe, your own email provider and your own model keys, and you keep those relationships if you ever leave.
Do integrations count towards my plan limits?
Calls to external services spend integration credits, which are included monthly with every plan. Building and testing a connection does not.