# Zapier Tables vs. @Human Namespaces/Compose ## Executive Summary Zapier Tables and @Human Namespaces/Compose represent two fundamentally different philosophies in data management and application building. Zapier Tables is an **automation-first, lightweight database** built tightly within the Zapier ecosystem, designed to store and trigger data flows across 8,000+ connected applications. @Human Namespaces/Compose is a **full-stack, open-source, self-hostable enterprise application builder** that treats data modules, pages, workflows, and access control as the building blocks of complete business applications. The two products serve overlapping but distinct audiences: Zapier Tables fits teams already embedded in Zapier's automation world who need simple, connected data storage; @Human Compose suits organisations that want to own their data infrastructure, build complex multi-module apps, and operate without vendor lock-in. *** ## 1. Platform Philosophy and Positioning ### Zapier Tables Zapier Tables launched as a data companion to Zaps and Interfaces, filling the gap for users who needed a simple place to store and reference data without leaving the Zapier platform. It is best described as an **automation-native spreadsheet-database hybrid** — records can trigger Zaps, buttons in a table can kick off multi-step automations, and AI fields can enrich records automatically. Tables is not positioned as a standalone application builder; its value proposition is almost entirely dependent on the wider Zapier ecosystem surrounding it. ### @Human Namespaces/Compose @Human Namespaces/Compose is a component of a broader open-source digital work platform. A **Namespace** in @Human is the top-level container for a self-contained business application — housing its own data modules, pages, charts, workflows, and access control rules. Multiple Namespaces can coexist on a single @Human instance, each functioning as an independent app. Because the platform is Apache 2.0 licensed, organisations retain full control of code, data, and deployment infrastructure, eliminating vendor lock-in. The platform is built with Go on the back end and Vue.js on the front end, making it fast and scalable. *** ## 2. Data Architecture and Modelling ### Zapier Tables: Simple Tabular Data Zapier Tables operates on a flat, single-level structure: each **Table** is a standalone grid of records with typed columns. Tables can be linked to each other through the linked records field, allowing basic relational references. However, the scope of each table is contained within the Zapier account, and there is no concept of grouping related tables into a higher-level application container. | Aspect | Zapier Tables | @Human Compose | | ------------------------- | ------------------------------------------ | ---------------------------------------------------------------------------- | | Data container unit | Table (flat grid) | Namespace → Module (hierarchical) | | Relationships | Linked Records field (paid plans) | Record Selector field (full relational links, multi-namespace via workflows) | | Data isolation | Per-account | Per-Namespace (cannot cross-access without workflow) | | External database support | None natively | DAL Connections: MySQL, PostgreSQL, and other RDBMS | | Record import | CSV, Google Sheets, Airtable, Excel, Slack | CSV/JSONL via CLI with definition YAML files | | Namespace/App export | Not applicable | Full namespace export/import as .zip (modules, pages, charts) | | Data sensitivity tagging | Not available | Up to 10 sensitivity levels per connection, module, and field | ### @Human Compose: Structured Relational Modelling Within each Namespace, @Human Compose uses **Modules** as the equivalent of database tables. Each Module defines typed fields and provides the foundation for record storage, CRUD operations, and automatic page generation. The platform's **DAL (Data Abstraction Layer)** allows administrators to connect external RDBMS databases — meaning @Human can read and write from existing enterprise data sources without migration. This is a critical differentiator for enterprises with legacy systems. @Human also introduces **data privacy at the schema level** through configurable sensitivity levels applied to connections, modules, and individual fields. For example, all records for a "Medical Notes" module can be directed to a dedicated encrypted database connection. This fine-grained privacy architecture goes far beyond anything available in Zapier Tables. *** ## 3. Field Types Both platforms support a range of field types, but @Human Compose offers a materially wider set suited to enterprise application scenarios. | Field Type | Zapier Tables | @Human Compose | | --------------------------- | ---------------------------------- | -------------------------------------------------------------------------------------- | | Text (single-line) | ✅ (255 char limit) | ✅ | | Long Text / Rich Text | ✅ (10,000 char limit) | ✅ (with Rich Text Editor option) | | Number | ✅ (7 decimal digits) | ✅ | | Currency | ✅ | ✅ | | Date & Time | ✅ | ✅ | | Checkbox / Boolean | ✅ | ✅ | | Dropdown / Select | ✅ | ✅ (static or dynamic values) | | Email | ✅ | ✅ | | Phone Number | ✅ | ✅ | | Link / URL | ✅ (2,048 char limit) | ✅ | | JSON | ✅ | ✅ | | Linked Record (cross-table) | ✅ (paid plans only) | ✅ (Record Selector, with prefilter, multi-value) | | Formula / Computed Field | ✅ (paid plans, via formula engine) | ✅ (expression engine; formula fields on modules) | | AI Field | ✅ (paid plans) | ❌ (native AI fields not built-in; can be implemented via workflows + external LLM API) | | Button (automation trigger) | ✅ (trigger or continue a Zap) | ✅ (automation page block with script/workflow trigger) | | File / Attachment | ❌ | ✅ | | User selector | ❌ | ✅ (can reference system users) | | Geometry / Coordinates | ❌ | ✅ (geographic data for data sovereignty map) | | Multiple values per field | ❌ | ✅ (per-field "Multiple values" toggle) | *** ## 4. Record Limits and Plan Structure Zapier Tables operates on a tiered pricing model with hard limits on tables, records, and views per plan. | Plan | Tables | Fields/Table | Records/Table | Views/Table | Price | | -------- | ------ | ------------ | ------------- | ----------- | ---------- | | Free | 5 | 100 | 2,500 | 3 | Free | | Pro | 20 | 200 | 100,000 | 50 | $20/month | | Advanced | 50 | 200 | 500,000 | 50 | $100/month | @Human Compose, being self-hosted and open-source, has **no platform-imposed limits on Namespaces, Modules, records, or fields**. The only constraints are those of the underlying database and server infrastructure managed by the operator. This architectural freedom is a decisive advantage for high-volume enterprise deployments. The platform's Apache 2.0 licence means there are no per-seat or per-record licensing fees. *** ## 5. User Interface and Page Building ### Zapier Tables: Spreadsheet-Style Grid The Zapier Tables interface is modelled on a familiar spreadsheet grid. Users can create **Views** — filtered and field-restricted perspectives of the same table data — to share with collaborators. Views can be saved and can even trigger automations, giving them functional value beyond display. There is no custom page builder in Zapier Tables itself; for richer interfaces, users must combine Tables with **Zapier Interfaces**, a separate product that allows embedding tables and views in custom layouts. ### @Human Compose: Full-Featured Page Builder @Human Compose includes a built-in, drag-and-drop **Page Builder** that allows users to assemble pages from a library of configurable block types. Pages are first-class citizens within a Namespace and form the navigable app interface visible to end users. Available page block types include: * **Record List Block** — display, filter, search, and interact with module records * **Record Detail Block** — view and edit a single record's full field set * **Chart Block** — embed line, bar, pie, doughnut, funnel, and gauge charts * **Calendar Block** — show records as events in month/week/day/agenda views * **Metric Block** — display calculated aggregate numbers (e.g., total leads, monthly revenue) * **Content Block** — static rich text, announcements, and help content * **File Block** — display attachments such as PDFs, brochures, and schedules * **IFrame Block** — embed external web content * **Automation Block** — surface manual workflow triggers as clickable buttons * **Reporter Block** — embed report data from @Human's Reporter module directly on a page This is a qualitatively different capability from Zapier Tables' grid view. @Human administrators can compose bespoke application dashboards that combine multiple data views, visualisations, and action triggers in a single, branded interface. *** ## 6. Charting and Reporting Zapier Tables has **no native charting or reporting** capability. Users must export data or use Zapier Interfaces and external tools to visualise table contents. @Human Compose supports **inline charts** built from module data and displayed directly on namespace pages. Supported chart types include standard line, bar, pie, and doughnut charts, as well as advanced funnel charts (composed across multiple modules) and gauge charts. Beyond in-page charts, @Human offers a dedicated **Reporter application** that provides a full report-building interface with drag-and-drop report blocks, data source configuration, and RBAC-controlled access to reports. Reporter blocks can be embedded directly on Compose pages, creating a seamless integration between application data and reporting output. *** ## 7. Automation and Workflow ### Zapier Tables: Automation via Zaps Zapier Tables participates in Zapier's broader automation ecosystem. Tables can act as **triggers** (when a record is created, updated, or a button is clicked) and as **actions** (create, update, or delete records). The **Button field** type allows inline one-click triggers from a record, launching either a new Zap or a step within an existing Zap. The **AI field** can automatically populate records with LLM-generated content based on other field values and a user-defined prompt. Automation in Zapier Tables is inherently coupled to the Zaps model — each automated process is a Zap step, benefiting from Zapier's 8,000+ app integrations but also bound to Zapier's task-count pricing model and cloud-hosted architecture. ### @Human Compose: Embedded Visual Workflow Engine @Human includes a fully integrated **visual workflow builder** that operates as a first-class platform component, accessible from the Admin area. Workflows are designed on a canvas using drag-and-drop nodes and support: * **Event-based triggers** — record creation, update, delete, manual user action, scheduled intervals * **Conditional branching** — if/else logic and expression-based routing * **Expression engine** — a Gval-based formula parser with custom functions for data manipulation * **Template rendering** — Go-template syntax for generating emails, PDF documents, and notifications * **Corredor scripting** — a server-side JavaScript execution engine (Node.js) for complex custom logic invocable from within workflows * **Unlimited workflows** — no cap on the number of automation processes per instance * **Audit log integration** — workflow sessions are logged for compliance and debugging @Human's automation is entirely self-contained on the operator's infrastructure, with no per-task charges and no dependency on a third-party cloud platform. The combination of visual workflows and JavaScript scripting allows a much wider range of automation complexity than Zapier Tables can achieve independently. *** ## 8. Access Control and Permissions ### Zapier Tables: Simple Role Model Zapier Tables offers three permission levels: **Owner** (full control, can create Zaps), **Editor** (full edit access), and **View Only** (read and export). In Team and Enterprise accounts, tables can be shared across the account; public share links provide view-only access. There is no granular record-level or field-level access control within Tables itself. ### @Human Compose: Enterprise-Grade RBAC @Human implements a comprehensive **Role-Based Access Control (RBAC)** system that governs access at multiple resource levels: * **System level** — who can create and manage Namespaces, workflows, and scripts * **Namespace level** — roles with access to a specific application * **Module level** — who can read, create, update, or delete records in a module * **Field level** — visibility and editability of individual fields per role * **Record level** — access control on specific records using context roles **Context roles** allow the system to dynamically assign users to roles based on record data — for example, a user is assigned the "Record Owner" role only for records they created, enabling fine-grained ownership-based access patterns. The RBAC evaluation follows a hierarchical rule precedence (bypass → context → common → authenticated → anonymous), ensuring predictable and auditable access decisions. This level of granularity is enterprise-standard and goes far beyond what Zapier Tables offers. *** ## 9. Integration and API Capabilities ### Zapier Tables The primary integration mechanism for Zapier Tables is the **Zap** — connecting Tables to 8,000+ external apps through Zapier's managed integration library. Zapier also supports **Webhooks** for receiving and sending HTTP requests. However, there is no public REST API for Zapier Tables records themselves that external systems can query directly without going through a Zap. ### @Human Compose @Human exposes a comprehensive **REST API** for all Compose resources — Namespaces, Modules, Records, Pages, Charts — allowing external systems to read and write data programmatically without any middleware layer. In addition, @Human's **Integration Gateway** allows administrators to define custom HTTP endpoints with authentication, rate limiting, and request validation rules. These custom endpoints can proxy requests to external services or trigger internal workflows, making @Human a bidirectional integration hub rather than just a data store. The Gateway supports both built-in filter logic and inline JavaScript for advanced request processing. | Integration Feature | Zapier Tables | @Human Compose | | ------------------------------ | ----------------------- | ------------------------------------------------------- | | External app integrations | 8,000+ via Zaps | Via Workflow + REST API calls (no managed marketplace) | | Native REST API for records | ❌ (indirect via Zaps) | ✅ (full REST API for all resources) | | Custom HTTP endpoints | ❌ | ✅ (Integration Gateway) | | Webhook ingestion | ✅ (via Zapier Webhooks) | ✅ (Integration Gateway as webhook receiver) | | Cross-instance data federation | ❌ | ✅ (Corteza Federation protocol for cross-instance data) | | MCP (AI agent protocol) | ✅ (Zapier MCP) | ✅ (@Human MCP) | *** ## 10. Deployment and Hosting | Aspect | Zapier Tables | @Human Compose | | ---------------------- | -------------------------- | -------------------------------------------------------- | | Hosting model | Cloud-only (Zapier SaaS) | Self-hosted (Docker, VPS, on-premises) | | Data residency control | None (data held by Zapier) | Full (operator chooses server location) | | Open source | ❌ Proprietary | ✅ Apache 2.0 | | Self-hostable | ❌ | ✅ | | Multi-database routing | ❌ | ✅ (DAL supports multiple RDBMS connections per instance) | | Uptime SLA | 99.99% (Zapier platform) | Operator-managed | | Digital sovereignty | ❌ | ✅ (designed for EU/GDPR data sovereignty) | For organisations in the EU or operating under strict data residency requirements, @Human's self-hosted architecture is a significant advantage. The platform explicitly supports W3C standards and open data formats to guarantee data portability, and its data privacy architecture — including geolocation tagging of data sources — aligns directly with GDPR compliance needs. *** ## 11. Scalability and Enterprise Readiness ### Zapier Tables Zapier Tables is well-suited for SMB and mid-market teams already using Zapier. The Advanced plan supports up to 500,000 records per table, which is sufficient for many operational datasets. Enterprise account features include table sharing across all users, Super Admin access, and custom limits. However, the platform lacks multi-tenancy, custom deployments, and the regulatory compliance controls typically required by large enterprises. ### @Human Compose @Human is architected for enterprise scale. A single instance can host **unlimited Namespaces** — each functioning as a separate business application — with record capacity limited only by the connected database. Features such as multi-database DAL connections, field-level data sensitivity tagging, comprehensive RBAC, workflow audit logs, and namespace export/import for templated deployments are purpose-built for complex organisations. The platform's API-centric design and open standards ensure interoperability with existing enterprise systems. *** ## 12. Collaborative Features | Feature | Zapier Tables | @Human Compose | | --------------------------------- | ---------------------------- | ---------------------------------------- | | Shared tables within account | ✅ (Team/Enterprise plans) | ✅ (RBAC-controlled at any plan) | | Public read-only share link | ✅ | ✅ (via public page settings) | | Field-visibility per collaborator | ✅ (via Views) | ✅ (via RBAC field rules) | | Record filtering per collaborator | ✅ (saved Views with filters) | ✅ (module prefilters + context roles) | | Multi-user concurrent editing | ✅ | ✅ | | User management | Zapier account users only | Full user/role management within @Human | | Audit trail | Zap task history | Workflow session log + system action log | *** ## 13. AI Capabilities Zapier Tables offers a native **AI Field** that lets users write a natural language prompt and have the LLM automatically populate field values based on other record data. This is a low-friction, no-code AI enrichment capability that distinguishes Zapier Tables from many competing lightweight databases. Summary formulas and formula fields on paid plans expand computed-field capabilities further. @Human Compose does not include a native LLM-powered field type. However, its workflow engine and Integration Gateway can be used to call external AI/LLM APIs (e.g., OpenAI, Mistral) and write results back to module records, enabling AI-augmented data pipelines for teams comfortable with moderate configuration. The platform has been identified as a strong architectural foundation for **agentic AI** use cases, where its data modules provide persistent state, workflows provide decision logic, and namespaces provide isolation for multi-agent deployments. *** ## 14. Templates and Reusability Zapier Tables provides a **template gallery** when creating a new table, covering common use cases (CRM pipeline, event tracker, lead list, etc.). Templates accelerate initial setup but are static starting points, not portable app bundles. @Human Compose supports **full namespace export and import** as a .zip archive containing all modules, pages, charts, and configuration. This allows entire applications to be packaged as reusable templates and deployed to different @Human instances. @Human also ships with a ready-to-use **CRM application** built entirely on its own platform as a reference implementation. Additionally, @Human provides a **document template system** (HTML and plain-text templates rendered via Go templating) for generating structured outputs like PDF quotes or email messages from workflow data. *** ## 15. Summary: Side-by-Side Decision Matrix | Capability Area | Zapier Tables | @Human Compose | | ------------------------ | ---------------------------------------- | ------------------------------------------------------- | | **Core purpose** | Automation-native lightweight database | Full-stack enterprise app builder | | **Data modelling depth** | Flat tables, basic linked records | Hierarchical Namespace → Module → Field, multi-DB | | **Field type richness** | Moderate (15 types, AI field on paid) | Comprehensive (20+ types, file, user, geometry) | | **Record limits** | Up to 500k/table (paid) | Unlimited (infrastructure-bound) | | **Page/UI builder** | None (grid view only; Interfaces needed) | Full drag-and-drop Page Builder with 10+ block types | | **Charting** | None | Inline + Reporter (line, bar, pie, funnel, gauge) | | **Automation** | Via Zaps (8,000+ app integrations) | Visual workflow builder + JS scripting engine | | **Access control** | 3 roles (Owner/Editor/View) | Fine-grained RBAC: system/namespace/module/field/record | | **Data sovereignty** | Cloud-only, no residency control | Self-hosted, configurable geolocation, GDPR-ready | | **Open source** | No | Yes (Apache 2.0) | | **API access** | Indirect (via Zaps/Webhooks) | Full REST API + custom Integration Gateway | | **AI capabilities** | Native AI field (paid) | Via external API + workflow integration | | **Pricing model** | SaaS subscription with usage limits | Free to self-host; commercial support optional | | **Namespace/App export** | Not applicable | Full .zip export/import | | **Learning curve** | Low (familiar spreadsheet UX) | Moderate (app-builder model with admin panel) | | **Best fit** | SMB teams deep in Zapier ecosystem | Enterprises needing owned, sovereign, complex apps | *** ## Conclusion The choice between Zapier Tables and @Human Namespaces/Compose ultimately reflects whether an organisation needs a **connected data layer** or a **complete application platform**. Zapier Tables excels when the primary goal is to store lookup data, track records, and trigger automations across a large portfolio of SaaS tools with minimal setup overhead. Its AI field and native Zap integration make it particularly powerful for lean automation-first teams. @Human Namespaces/Compose is the superior choice wherever data ownership, security depth, application complexity, or regulatory compliance are non-negotiable. Its ability to host multiple full applications within a single instance, route data across multiple external databases, enforce granular RBAC at the field level, and deploy entirely on an organisation's own infrastructure positions it as a genuine enterprise platform — not merely a database tool. For organisations building towards agentic AI architectures, @Human's composable module/workflow/namespace model provides a structurally sound foundation that Zapier Tables, by design, was never intended to offer. ## References 1. [Compose Low-Code Platform | cortezaproject/corteza-docs | DeepWiki](https://deepwiki.com/cortezaproject/corteza-docs/3.2-compose-low-code-platform) - Corteza Compose is a low-code application development platform that enables users to build custom bu... 2. [Zapier vs. Airtable: Which is best? \[2026\]](https://zapier.com/blog/zapier-vs-airtable/) - Here's a full comparison to help you understand Zapier's and Airtable's strengths, how to choose bet... 3. [What to Know About Zapier’s New Tables Product](https://www.browserbear.com/blog/what-to-know-about-zapiers-new-tables-product/) - Tables enables you to store, edit, track and move your data across sources. Here's what you need to ... 4. [Zapier Tables: Store, move, and take action on your data automatically](https://zapier.com/blog/zapier-tables-guide/) - Say goodbye to spreadsheet workarounds and say hello to Zapier Tables, the automation-first database... 5. [Build Your Enterprise Systems On Corteza Low-Code! - Planet Crust](https://www.planetcrust.com/build-your-enterprise-systems-on-corteza-low-code/) - Corteza Low-Code represents a strategic platform for organizations seeking to accelerate enterprise ... 6. [How to create a namespace in Corteza](https://www.youtube.com/watch?v=80ykpVBzDgw) - 💡 HOW TO CREATE A NEW LOW-CODE APP IN CORTEZA 🔽 In this tutorial we'll show you how to create a ne... 7. [What are Namespaces in Corteza? | Scribe](https://scribehow.com/viewer/Corteza_20249_What_are_Namespaces_in_Corteza__OuOu0wTbSCOe5MNVK904uw) - By Niall McCarthy 8. [Getting started with Corteza Low Code for your CRM - Open Source](https://opensource.com/article/19/9/corteza-low-code-getting-started) - This three-article series will explain, step by step, how to build a sample application to manage do... 9. [The Ultimate Guide to Zapier Tables | XRAY Blog](https://www.xray.tech/post/ultimate-guide-zapier-tables) - With Zapier Tables, you can create a simple database for your Zaps and Interfaces. In this guide, we... 10. [Zapier Tables Just Got a GAME CHANGER with Linked Records!](https://www.youtube.com/watch?v=-dA1HSPnV3Y) - Zapier Tables just got a game changer with linked records! You can now link records from one Table t... 11. [How to create the data structure for a Corteza Low Code application](https://opensource.com/article/19/10/corteza-low-code-data-structure) - Corteza is an open source alternative to Salesforce. Learn how to use it in this series. 12. [Low Code configuration - Corteza Docs](https://docs.cortezaproject.org/corteza-docs/2021.3/integrator-guide/compose-configuration/index.html) - By configuring your Low Code, you define the logical data structure and its representation. This pag... 13. [DAL Connections - Corteza Docs](https://docs.cortezaproject.org/corteza-docs/2024.9/integrator-guide/dal-connections/index.html) - DAL connections (also referred to as connections) define a location where Corteza can store and retr... 14. [Whats New - Tables Feedback Portal - Zapier](https://tables-feedback.zapier.app/whats-new) 15. [Import Low Code Records - Corteza Docs](https://docs.cortezaproject.org/corteza-docs/2024.9/devops-guide/examples/cli/record-import.html) - Use the import CLI command to import your records. The argument to the CLI command needs to be the l... 16. [Importing and exporting namespaces - Corteza Docs](https://docs.cortezaproject.org/corteza-docs/2024.9/integrator-guide/compose-configuration/import-export.html) - Corteza makes it easy to export entire namespaces which can then be imported into an entirely differ... 17. [Sensitivity Levels](https://docs.cortezaproject.org/corteza-docs/2023.9/integrator-guide/data-privacy/sensitivity-levels.html) - Learn how to introduce data privacy policies to your Corteza Low Code application 18. [Corteza: Free Open Source Low Code Platform - Elestio blog](https://blog.elest.io/corteza-free-open-source-low-code-platform/) - A revolutionary open-source low-code platform that promises to transform the way organizations devel... 19. [Corteza Privacy - Architecture and Work Plan](https://cortezaproject.org/corteza-privacy-architecture-and-work-plan/) - Geolocation of Data Sources All data source definitions (primary, compose record store, federation) ... 20. [Zapier Tables usage limits](https://help.zapier.com/hc/en-us/articles/15721386410765-Zapier-Tables-usage-limits) - Zapier Tables have specific limits that affect the number of tables, records, or fields you can crea... 21. [Building data modules](https://www.planetcrust.com/help/tutorials/building-data-modules) 22. [Different field types in Zapier Tables](https://help.zapier.com/hc/en-us/articles/9775472454157-Different-field-types-in-Zapier-Tables) - Zapier Tables has different field types that provide features like formatting data or triggering Zap... 23. [Field Types and Editors | cortezaproject/corteza | DeepWiki](https://deepwiki.com/cortezaproject/corteza/5.1-field-types-and-editors) - This document covers Corteza's field type system and the editor components that provide user interfa... 24. [Use formulas in Zapier Tables](https://help.zapier.com/hc/en-us/articles/34043499167117-Use-formulas-in-Zapier-Tables) - Available on plans: Free Pro Advanced The Formula field in Zapier Tables allows you to create calcul... 25. [Automation and Workflows | cortezaproject/corteza-docs | DeepWiki](https://deepwiki.com/cortezaproject/corteza-docs/3.4-automation-and-workflows) - This document covers Corteza's automation and workflow system, which provides both visual workflow b... 26. [New: Create AI fields in Zapier Tables](https://zapier.com/blog/create-ai-fields-in-tables/) - Tables' new AI field lets you create an AI prompt, reference your data, and populate records—directl... 27. [Use the Button field in Zapier Tables](https://help.zapier.com/hc/en-us/articles/15720961080717-Use-the-Button-field-in-Zapier-Tables) - Button fields in Zapier Tables allow you to trigger Zaps or run actions within a Zap from a table by... 28. [Page block reference](https://docs.cortezaproject.org/corteza-docs/2021.3/integrator-guide/compose-configuration/page-blocks.html) 29. [Zapier Pricing Review 2025: Plans & Costs Explained - Tekpon 2026](https://tekpon.com/software/zapier/pricing/) - Explore Zapier pricing. Learn about features and costs to find the plan that best suits your Workflo... 30. [Zapier Tables Tutorial - Lead routing automation](https://www.youtube.com/watch?v=F2jITxcCdi4) - Curious about how you can enhance your business logic using Zapier Tables? Are they a suitable alter... 31. [Share Zapier Tables With Your Clients And Teammates - YouTube](https://www.youtube.com/watch?v=_ek-O2sfzxY) - that they can view and edit the data, simply use Zapier Interfaces! It's free and allows you to embe... 32. [Learn the Basics of Pages - Corteza](https://aireapps.com/tutorial/learn-the-basics-of-pages-in-corteza/) - Learn how to build customized pages in Corteza and create an engaging user experience with interacti... 33. [Low Code configuration - Corteza Docs](https://docs.cortezaproject.org/corteza-docs/2024.9/integrator-guide/compose-configuration/index.html) - A funnel chart is constructed from a series of reports where each report may define its dimension an... 34. [Corteza Discovery, Compose-Reporter Integration and more.](https://www.planetcrust.com/planet-crust-releases-corteza-2022-3-corteza-discovery-compose-reporter-integration-and-more/) - 2022.3 adds integration between the low-code app builder Corteza Compose and Corteza Reporter by int... 35. [Reporting - Corteza Docs](https://docs.cortezaproject.org/corteza-docs/2024.9/integrator-guide/reporting/index.html) - Corteza Reporter allows you to create beautiful reports using the data stored in your Low Code appli... 36. [Triggers and Actions for Zapier Tables | Customized Workflows](https://www.youtube.com/watch?v=FQIOaTjGZFk) - Zapier Tables expands automation possibilities within Zaps by acting as both triggers and actions. T... 37. [Corteza 2024.9 Admin Area: Automation Settings Overview](https://scribehow.com/viewer/Corteza_20249_Admin_Area_Automation_Settings_Overview__BQNKCd7rSsORuanN_G3L8Q) - By Niall McCarthy 38. [Templates - Corteza Docs](https://docs.cortezaproject.org/corteza-docs/2024.9/integrator-guide/templates/index.html) - Templates allow you to define the generic document structure (such as a welcome email message or a q... 39. [Passing Custom Arguments](https://docs.cortezaproject.org/corteza-docs/2024.9/integrator-guide/automation/workflows/automation-scripts.html) - Learn how to combine automation scripts with workflows to execute complex operations 40. [Manage permissions and sharing in Zapier Tables](https://help.zapier.com/hc/en-us/articles/16021760381453-Manage-permissions-and-sharing-in-Zapier-Tables) - Limitations · Table views can only be shared as View only. · Sharing a table with another user does ... 41. [Access control](https://docs.cortezaproject.org/corteza-docs/2021.9/integrator-guide/access-control.html) 42. [The Security Model](https://docs.cortezaproject.org/corteza-docs/2024.9/integrator-guide/security-model/index.html) - Learn how to configure your security model to conform to your business requirements 43. [How to get started with Webhooks by Zapier](https://help.zapier.com/hc/en-us/articles/8496083355661-How-to-get-started-with-Webhooks-by-Zapier) - Introduction to webhooks Zapier fully supports webhooks, and though they can be a little overwhelmin... 44. [Integration Gateway](https://docs.cortezaproject.org/corteza-docs/2023.9/integrator-guide/api-gw/index.html) - Lean how to define custom API endpoints using the integration gateway 45. [Integration Gateway - Corteza Docs](https://docs.cortezaproject.org/corteza-docs/2024.9/integrator-guide/api-gw/index.html) - Lean how to define custom API endpoints using the integration gateway 46. [Corteza Gateway](https://www.planetcrust.com/corteza-gateway) - Corteza, the leading open-source low-code development platform just had the first release of its rou... 47. [corteza-server module - github.com/cortezaproject ...](https://pkg.go.dev/github.com/cortezaproject/corteza-server) 48. [How much does Zapier cost in 2026? A complete guide to pricing ...](https://www.electricmonk.com/zapier-pricing-2026/) - If you’re reading this, you’ve probably reached the “OK, but how much is Zapier actually going to co... 49. [Intro to Corteza, an open source alternative to Salesforce](https://opensource.com/article/19/8/corteza-open-source-alternative-salesforce) - Corteza is an open source, self-hosted digital work platform for growing an organization's productiv... 50. [Your New Secret Weapon: Formulas in Zapier Tables (Game Changer!)](https://www.youtube.com/watch?v=3bs9polq7dw) - Your new secret weapon: Formulas in zapier tables (Game changer!) Formulas are now in Zapier Tables!... 51. [Imagining Corteza as an Agentic AI Low-Code Platform - Aire](https://aireapps.com/articles/imagining-corteza-as-an-agentic-ai-low-code-platform/) - In short, Corteza's data modules provide the tables and records that an autonomous agent uses to kno... --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.planetcrust.com/price-and-terms/product-comparisons/zapier-tables-vs.-human-namespaces-compose.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.