Platform

No-code platform for databases, forms, portals and workflows

Structure your data, capture information, automate processes and let people decide where it matters — in one platform, without programming.

Build your own database

ApptiveGrid's visual database follows your structure instead of forcing you into someone else's schema. You create grids, pick the right type for every column and link related entries to each other.

  • 26 column types — text, number, currency, date, select, files, address, geolocation, signature and more
  • Links between grids — a customer and their orders, a vehicle and its inspections — a real relation instead of copied text
  • Computed fields — formula, calculate sum and take value keep themselves up to date
  • Collaboration — several people work in the same grid at once, roles govern who may do what
Database in detail
Customer
Text
Order status
Single select
Due date
Date
Documents
Files
Total
Formula
+ Add field

One database, seven views

The same data, shown the way the task needs it. Every view has its own filters, sorting and hidden columns — without changing anything about the data itself.

Table

The classic spreadsheet view. All your data structured at a glance.

Kanban

Made for tasks and projects. Make status and progress visible.

Calendar

For scheduling and deadlines. Keep every date in sight.

Map

Address and geo data on an interactive map instead of in a column.

Gallery

Photos from file fields as tiles — ideal for inventory and documentation.

List

A compact list for a quick overview of many entries.

Timeline

Plan projects over time and spot dependencies.

Exactly the form you need

A form comes straight out of a grid: pick the fields, name them for the people who fill them in, and share the result by link, QR code or embedded on your website. Every response lands as an entry in your database.

  • Required and hidden fields — hidden fields are still submitted — location or source, for instance
  • Prefilled links — device, vehicle or contact are already filled in when the form opens
  • File, video and signature fields — evidence straight from the phone, without a detour through email
  • After submitting — your own success page, a redirect to your website, or straight into the next form
Forms in detail

Maintenance log

Live

Your portal — minutes instead of weeks

Pages are assembled from blocks: headings, text and images, embedded views and evaluations, buttons and input fields. Published, a page becomes a portal under its own address — for customers, partners or your own team.

  • Three block groups — basic blocks for layout, special blocks for views, evaluations and buttons, form field blocks for input
  • Tab and stepper layout — subpages as tabs, or a guided process step by step
  • Conditional visibility — blocks appear only when they fit the situation
  • Portal link — share it or embed it in your own site — responsive on every device
Pages & portals in detail
portal.mycompany.com
OverviewRequestsArchive

Automate the work that repeats

A flow is a trigger plus as many steps as you need, assembled visually — from a notification on a new entry to a multi-step chain across several systems.

  • Six triggers — new entry, changed entry, entry via form, entry changed via form, webhook, page displayed
  • Data — create and update entries, load every entry of a grid
  • Communication — email, HTTP request, Slack, MS Teams, Firebase, Hubspot, SMS through Magenta Business
  • Generate — QR code, Document Analyzer, PDF and speech to text, URL to PDF, CSV import, calendar entry, DATEV file
Automation in detail
Trigger: Entry via form
Someone submits the maintenance log
Action: Update entry
Set status to “In review”
Action: Send email
Notify the responsible team
Action: Slack message
Post to #maintenance

Pages as a flow step: processes that wait for people

Not every process finishes in a second. A flow step can display a page with form fields — or create a link to that page and send it by email. The flow pauses until someone has decided, then carries on. That is how long-running approval processes work without anyone needing another account.

  • Approvals and reviews — leave requests, purchases, defect reports — nothing moves before the decision
  • A link by email — the person deciding clicks in their inbox and needs no access to the platform
  • Form fields on the page — a comment, a reason or a correction flows back into the entry
  • Traceable — who decided what and when lives in the entry, not in an email thread
Approvals in detail
Trigger: New entry
A purchase request arrives
Action: Create link to a page
Send it to the manager by email
Approval
The flow waits until someone decides.
waiting
Comment
Approve
Reject
Action: Update entry
Write the decision back — the flow continues
AI in workflows

Use AI deliberately, not accidentally

In ApptiveGrid, AI is a step inside a flow rather than a separate tool beside it. “OpenAI” and “Document Analyzer” are ready to use, the result is written into fields of the entry, and it can be put up for approval before anything else happens.

  • OpenAI without a contract — the step runs through ApptiveGrid — no API key, no separate billing
  • Document Analyzer — reads attached documents and returns the values they hold
  • Result in the entry — a category, a summary or a draft lands in fields and stays reportable
  • Approval first — a page as a flow step puts the suggestion up for review
  • Open to others — any further AI service can be connected through an HTTP request
AI in workflows in detail
Entry
Support request #4812
Action: HTTP request
Hand the text to the AI service of your choice
Result in the entry
Category Billing
Summary Customer asks for a corrected invoice for March.
Review before it counts
A page shows the suggestion; the flow only continues once it is approved.

Questions about the features

How many field types does an ApptiveGrid database have?

26 column types — from text, number, currency and date through single and multiple select, files, address, geolocation and signature to linked entries and computed fields such as formula or sum.

What is the difference between a form, a view and a page?

A form is built for quick data capture, a view displays data you already have. A page combines both: text, embedded views, input fields and evaluations in a freely composed layout — published as a portal under its own address.

What triggers an automation?

Six triggers: a new entry, a changed entry, an entry created through a form, an entry changed through a form, a webhook from an external system, and a page being displayed.

Can a process wait for a human decision?

Yes. A flow step can display a page, or create a link to that page and send it by email. The process pauses until someone decides and continues afterwards — even days later.

How does AI fit into a process?

Through ready-made flow steps: “OpenAI” sends a prompt to ChatGPT, the “Document Analyzer” reads attached documents. Both belong to the Pro plan, and OpenAI needs no contract of your own. Any other AI service can be connected through an HTTP request. The result is written into fields and can be approved on a page before anything else happens.

Can I connect the systems we already use?

Yes — through Zapier and Make, the REST API and webhooks in both directions. Inside a flow you can also send arbitrary HTTP requests and reach Slack, MS Teams, Firebase, Hubspot, Magenta Business SMS and DATEV.

Start for free today

Try every feature at no cost. No credit card required.