Tadabase

Tadabase is a no-code database and application builder with data tables, pages built from components, scheduled tasks, exports and PDF templates. Agents read and write records, attach files, recalculate equations, run scheduled tasks, submit form components and generate exports and PDFs.

47 actions API key available

Tadabase website Platform Documentation Capability data verified 2026-08-27

An inspection report arrives from the field and needs to enter the application

List Page Components resolves the form component the office team normally submits through

Count Matching Records checks whether an open record already covers this site and date

Submit Form Component writes it the way a person would, so the form's rules and record rules run

Attach File To Record From URL points the file field at the photo set without moving the bytes

Generate PDF From Page renders the completed report for the client file

The supervisor reviews the rendered report before it leaves the building

What This Integration Enables

Tadabase is a no-code application builder, and this connector reaches the application rather than only the table underneath it. That distinction runs through the whole surface. Get Component Records returns what a user would actually see on a page, with the component's own filters, sorting, and Pipes already applied, which is not the same as reading the raw table. Submit Form Component submits the way an end user would, so the form's rules and record rules all run, and the README is blunt that writing the same fields through Create Record bypasses every one of them. An agent working here gets to choose whether it is editing a database or using an application, and on a platform where the business logic lives in the pages, that choice is the whole game.

The reach goes further than records. FlowRunner agents can start and follow the application's own scheduled tasks, terminate a run that is going wrong, read eight audit logs through one operation, run export templates and wait on their queue, render PDF pages laid out for print, and fill the form fields inside existing PDF documents. They can also sign an end user in and act with that user's visibility, which is how a read returns what that person is allowed to see instead of the unrestricted set. Each of those is a capability the connector is built and verified against the vendor's official API to provide, and each of them raises the same question FlowRunner exists to answer: which of these should an agent be allowed to do without asking.

Without FlowRunner

Two ways in, one of them wrong Records written straight to the table skip the form rules, Pipes, and record rules the application depends on

Reports assembled by hand Someone opens the app, filters a view, exports it, and reformats the result into something a client can read

Access handed out by password Giving an outside party a look at their own records means creating an account and mailing credentials

With FlowRunner

Writes that behave like people Submitting through the form component runs the same logic a user's submission would

Documents rendered from the app Exports and PDFs are produced from templates the team already maintains, on the flow's schedule

Access as a deliberate act A sign-in link is issued for a named person and a named reason, with someone accountable for issuing it

Use Case Scenarios

Field reports that arrive already validated

An inspection report comes in from the field, as an email in Gmail or a file drop. The agent extracts the readings, calls Count Matching Records to check no open record already covers this site and date, and then calls Submit Form Component rather than Create Record, because the application's form carries the conditional rules that decide severity and routing. Attach File To Record From URL points the file field at the photo set so Tadabase fetches it directly and a large upload never passes through the flow. Where the reading crosses a threshold, the flow posts to Slack instead of closing the record.
The Monday export nobody runs

A weekly export template already exists in the builder, with the right table, fields, and filters. The agent calls Run Export Template, receives a queue identifier, polls Get Export Queue Item until it reports finished, and reads the download link from Get Export. The file lands in a sheet in Google Sheets and a link posts to the team channel. Tadabase keeps exports for a limited window rather than indefinitely, so the flow collects the file rather than assuming it will be there next week.
A document the client can sign

Once a job record reaches its completed state, Generate PDF From Page renders the details page for that record into a document laid out for print, using the template the team maintains inside Tadabase. Generate PDF Form covers the other case, where an existing PDF has form fields that need filling and the field names come from the document itself rather than from a table. The rendered file goes into a signature request in DocuSign, and the signed copy comes back to the record.

Human-in-Loop Highlight

Create Magic Link issues a single use sign-in link for one of the application's own end users, so a flow can email someone straight into the application without asking for a password. It is enormously useful and it is not a data operation. It is a credential, and once it has been sent it exists on its own: it is in an inbox, it may have been forwarded, and nothing in the flow can call it back. Log Out End User invalidates a token that was issued through a login, which is not the same as unsending a link.

So the agent prepares everything and stops at the send. It resolves the end user, confirms with Get End User Session that the identity is the one intended, drafts the message, and then asks: "This will issue a sign-in link for the end user at this address and email it to them, giving whoever opens it that user's view of the application. The address on the record was changed 3 days ago. Send, or verify the address first?" A person answers. The agent is a perfectly good judge of whether a record is complete. It is not a judge of who should be signed in as whom, and the operations on this connector that grant access, rather than read or write data, are the ones FlowRunner keeps in front of a human by default.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

47 actions

Account

Check API Status Confirms that the configured App ID, App Key, and App Secret are accepted. Worth using as the connection test, because every other route answers the same authentication error and gives no hint which of the three is wrong.

Tables and Roles

List Tables Lists the data tables in the application with the identifier each record operation needs. Table identifiers are short opaque strings rather than the name shown in the builder.
List User Roles Lists the user roles defined in the application, with the identifier a Users table record needs when it sets a role.

Records

List Records Reads records with filtering, sorting, field selection, and pagination. Tadabase returns at most 100 records per page whatever limit is asked for, so a larger table has to be walked page by page.
Get Record Reads one record by its identifier.
Create Record Adds a record to a table, with fields keyed the way Tadabase names them rather than by label. Note that this bypasses the form rules and record rules an application carries.
Update Record Changes the named fields on one record and leaves every other field untouched. Tadabase updates with POST rather than the usual verb, which a client built on convention reaches nothing with.
Delete Record Permanently removes one record from a table.
Count Matching Records Reports how many records a set of filters matches, without reading them. Tadabase intends this as the check to run before a batch update, so a flow can see the size of what it is about to change.
Attach File To Record Uploads a file into a file field on an existing record, from FlowRunner file storage or from a URL. An image field is the exception and is set through Update Record instead.
Attach File To Record From URL Points a file field at a file Tadabase should fetch itself, so a large file never moves through the flow.

Equations

Recalculate Table Equations Recalculates every equation field in a table. Paired with the skip-equations option on a write, which is much faster, and brings the table up to date once the writes are finished.
Recalculate Field Equation Recalculates a single equation field across the table it belongs to, rather than every equation in the table.

Logs

Get Log Reads one of the application's audit logs. Tadabase publishes eight of them behind a single route differing only in its last segment, so they are one operation with a log type rather than eight near-identical ones.

Scheduled Tasks

List Scheduled Tasks Lists the scheduled tasks defined in the application, with the identifier the other task operations need.
Get Running Task Status Reports the status of every task currently running. The check to make before triggering a task that may already be in progress.
Get Task Status By Task Reports the current status of one scheduled task, identified by the task itself.
Get Task Status By Job Reports the status of one particular run. Run Scheduled Task answers with a job identifier, and this is how a flow follows that run to completion.
List Task History Lists past runs of every scheduled task in the application.
Get Task History By Task Lists past runs of one scheduled task.
Get Task History By Job Reads the recorded outcome of one particular run, including what it did rather than only whether it finished.
Run Scheduled Task Starts a scheduled task immediately instead of waiting for its schedule, and answers with the job identifier of that run.
Terminate Task Run Stops a run that is in progress. Work the run has already committed is not rolled back, so a partially completed run leaves its changes in place.

End User Authentication

Log In End User Signs one of the application's own end users in and returns a bearer token for them. That token is what the page and component operations pass so a read returns what that user is allowed to see.
Log Out End User Invalidates an end user's bearer token before its lifetime expires.
Get End User Session Reports whether an end user's token is still valid and which user it belongs to.
Create Magic Link Issues a single use sign-in link for an end user, so a flow can email someone straight into the application without a password. The operation this page's human gate exists for.

Pages and Components

List Layouts Lists the application's layouts, which are the top level containers its pages sit in.
List Pages Lists the application's pages, with the identifier the component operations need.
List Child Pages Lists the pages nested beneath one page, such as the detail pages a list page links through to.
List Page Components Lists the components on a page, such as tables, forms, and charts, with the identifier the record and form operations need.
Get Component Records Reads the records a component displays, with the component's own filters, sorting, and Pipes already applied. That is what a user would actually see, as opposed to the raw table. Component identifiers are the bare number.
Submit Form Component Submits a form component the way an end user would, so the form's rules, Pipes, and record rules all run. Preferred over Create Record whenever the application carries logic.

Exports

List Exports Lists the exports the application has produced. Tadabase keeps them for a limited window rather than indefinitely.
Get Export Reads one export, including the link its file can be downloaded from.
List Export Templates Lists the reusable export definitions configured in the builder, each deciding which table, fields, and filters an export covers.
Get Export Template Reads one export template's configuration.
Run Export Template Starts an export from a template. The file is produced in the background, so this answers with a queue identifier rather than the file.
Get Export Queue Status Reports the state of the export queue as a whole.
Get Export Queue Item Reports the state of one queued export, which is how a flow waits for a template run to finish.
List Export Queues Lists every queued export and its state, rather than one at a time.

PDF

List PDF Pages Lists the PDF page definitions in the application. A PDF page is a Tadabase page laid out for print.
Get PDF Page Reads one PDF page definition.
Generate PDF From Page Renders a PDF page to a file. Supply a record identifier for a details style page, or leave it empty for a list style page that renders the whole configured set.
List PDF Forms Lists the fillable PDF forms uploaded to the application. These are existing documents whose form fields Tadabase can populate, as opposed to pages it renders from scratch.
Get PDF Form Reads one PDF form, including the names of the fields inside the document that can be filled.
Generate PDF Form Fills a PDF form's fields with supplied values and returns the completed document. Field names come from the PDF itself rather than from a table.

Frequently Asked Questions

What can FlowRunner do with Tadabase?

FlowRunner agents can run Check API Status, List Tables, and List User Roles in Tadabase, plus 44 more actions.

Does connecting Tadabase to FlowRunner require OAuth?

No. Tadabase connects to FlowRunner with an API key, no OAuth flow required.

Can Tadabase trigger a FlowRunner workflow automatically?

Tadabase doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Tadabase

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us