Setu for SaaS "connect your apps"
Your customers connect their own apps. Setu keeps the tokens and runs the actions.
solutions-saas-connectThe problem
Building OAuth for every app, storing tokens safely and noticing when a connection breaks takes time away from your product.
What you can do
- Send each customer a link to connect Gmail, Calendar or Drive.
- Run actions with each customer’s own account, never a shared one.
- Get a webhook when a connection is revoked or needs attention.
- Start a workflow when a customer gets a new email.
The parts you use
Connect links
BetaSend your users a link to connect their own apps. Setu keeps the tokens and tells you when a connection breaks.
Learn more about Connect linksToolkits and actions
BetaRun actions in Gmail, Calendar, Drive, Docs, Tasks, Sheets and more. Write actions wait for approval.
Learn more about Toolkits and actionsWebhooks and triggers
BetaGet app events, finished runs, approvals and spend alerts sent to your server, with replay for failed deliveries.
Learn more about Webhooks and triggers
Create a connect link
Replace $SETU_API_KEY with a key from the Setu console.
# 1. Register your user once (your own id for them).
curl https://setu.supremeai.services/api/setu/external-users \
-H "Authorization: Bearer $SETU_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "externalId": "customer_42" }'
# 2. Create a connect link for an app. Send the returned "url" to the user.
# The link is valid for 10 minutes.
curl https://setu.supremeai.services/api/setu/connect-sessions \
-H "Authorization: Bearer $SETU_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "externalId": "customer_42", "toolkitSlug": "gmail" }'You stay in control
Your server keeps only your Setu key. Connect links last 10 minutes, and each connection belongs to one customer and one project.
What it costs
No Setu fee during beta. Calls use the credits in your SUPREME AI account.