Integrations
Your App, Connected to Everything It Needs
Apps built with Greta.sh plug straight into AI models, Slack, email providers, GitHub, and deployment platforms — no API keys to wrangle, no glue code to write.
Explore Integrations
Every integration works out of the box inside your Greta.sh app — with detailed guides, use cases, and example flows.
AI Models
How integrations work in a Greta.sh app
An integration here is not a webhook you have to wire up. When your app needs to post to Slack, send an email, call a model or read a repository, you describe that in the same plain English you used to build the app, and the connection is set up with credentials managed for you — no API keys stored in your own code, no OAuth flow to implement, no token refresh to maintain.
What you do not have to build
The work that normally sits between an app and a third-party service is the part that gets skipped: storing secrets safely, refreshing expired tokens, retrying failed calls, handling rate limits, and keeping up when a provider changes its API. Those are handled at the platform level, which is why an integration is a sentence rather than a sprint.
Start from what the app needs to do
The useful question is not "which integrations are available" but "what should happen automatically". A hiring tracker that emails a candidate when their stage changes needs an email provider. An internal dashboard that alerts a channel when a number crosses a threshold needs Slack. Work backwards from the behaviour and the integration you need becomes obvious.
- Notify a person or a channel when a record changes
- Send transactional email from inside the app
- Call an AI model on data the app already holds
- Read from or write to a repository
- Deploy the app somewhere it can be used
Adding one later is not a rebuild
Integrations are added to a working app the same way features are: by describing them. You do not need to know on day one which services you will connect, and choosing wrong is not expensive — swapping an email provider or adding a second notification channel is a change, not a migration.
Common questions
Do I need my own API keys?
No. Credentials are managed by the platform, so you do not store provider secrets in your app or rotate them yourself. You can still connect your own account where a service requires it.
Can I connect a service that is not listed?
Anything with an HTTP API can be called from an app you build here. The listed integrations are the ones with the setup work already done; the rest are a description away.
Does an integration slow the app down?
Calls to third-party services run server-side rather than in the browser, so a slow provider does not block the interface. Long-running work runs in the background.
Build Something Real
If you can describe it, you can build it.