ByteForms
5 operations0 webhooks
ByteForms plugin for Corsair
Supported operations
- CreateWrite
Create a new ByteForms form with custom fields and options
- DeleteDestructive
Delete a ByteForms form by its numeric or public ID
- GetRead-only
Retrieve a single ByteForms form definition by ID
- ListRead-only
List all ByteForms forms created by the authenticated user
- ResponsesRead-only
Retrieve paginated responses submitted to a ByteForms form
FAQ
Install corsair and @corsair-dev/byteforms, add the ByteForms plugin, and connect with an API key. Then call methods like corsair.byteforms.api.forms.create() from your app. Corsair keeps each tenant isolated.
Yes. ByteForms requires an API key from your ByteForms 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 ByteForms, GitHub, Notion, Stripe, and the rest. Trigger ByteForms from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for byteforms plugin for corsair. Common builds include sync jobs, admin tooling, and agents that call ByteForms APIs from your backend.
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 ByteForms 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/byteforms in the open repo. When ByteForms 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 ByteForms data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store ByteForms data on your behalf.