Tally

Install corsair and @corsair-dev/tally, add the Tally plugin, and connect with an API key. Then call methods like corsair.tally.api.forms.create() from your app. Corsair verifies webhooks, and syncs data per tenant.

Yes. Tally requires an API key from your Tally account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Tally, GitHub, Notion, Stripe, and the rest. Trigger Tally from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for simple form builder for surveys, signup flows, and collecting responses without code. Common builds include sync jobs, admin tooling, and agents that call Tally APIs from your backend. Webhook handlers react to Tally events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced Tally records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Tally API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/tally in the open repo. When Tally ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Tally data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Tally data on your behalf.