Data & Storage · Integration
Submittable
Add Submittable to your product for your customers, and give your AI agents governed access to it.
Submittable runs the intake side of grants, applications and open calls: an organisation builds its own forms, groups them into projects, collects submissions against them, then routes each one through multi-stage review with scores and decisions attached. Every field on every form was designed by that organisation, which is what an integration has to be designed around. There is no standard schema to code against, so which field carries the requested amount, the applicant's organisation or the eligibility answer is mapped per customer and per project rather than fixed in your product. Submissions also arrive in bursts against a deadline, so reads are paginated and paced. fastn looks after the credentials and pins every field mapping to the organisation it was built for.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each organisation connect their own Submittable account so applications reach your product without a spreadsheet in between.
Map each project's own form fields per customer, since two funders never ask for the same things in the same order.
Read review scores and decisions so the next steps in your product run on what reviewers actually concluded.
React when a submission arrives or changes stage, and pace reads through a deadline burst rather than polling harder.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises an application against the eligibility answers on its own form.
An agent reports which submissions have no reviewer assigned with the deadline approaching.
An agent writes a decision or a note back within scoped permissions, with the change attributed.
Example prompt
Which applications in this round are still unreviewed, and what did each one request?
Set up Submittable in 4 steps
- 01Enable the Submittable connector in your fastn dashboard.
- 02Have each organisation authorise their own account so submissions are read under their credentials.
- 03Map the project, form field, review score and decision values your product uses, per organisation.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Submittable integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Submittable integration without building it. Your customers connect their own Submittable account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Submittable update is not your on-call problem.
- One integration serves your product and your agents. The same governed Submittable connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
FormAssemblyWorks well with
Classy
DonorPerfectOften used alongside
Tools the same teams tend to run next to Submittable, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceSubmittable integration FAQ
How do I add a Submittable integration to my product?
Enable the Submittable connector in your fastn dashboard, then let each customer authenticate their own Submittable account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Submittable client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Submittable account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Submittable account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Submittable integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent summarises an application against the eligibility answers on its own form.
Who maintains the Submittable integration?
fastn does. When Submittable changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Submittable integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Submittable reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Submittable integration?
A common starting point: let each organisation connect their own Submittable account so applications reach your product without a spreadsheet in between. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Submittable integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Submittable does not change your per-connector cost. You can start free with 3 connected accounts.
Add Submittable to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.