Is Zapier Interfaces the same thing as Zapier Forms?

Yes, it was renamed. Zapier's help article on creating forms opens with a note saying Zapier Interfaces is now Zapier Forms, that existing projects still work exactly the same, and that all features continue to be available. The old name is still what most people search for and still appears in older community posts, so you will meet both. If you are hunting for a screen in the product today, search the help centre for Forms.

Do Zapier Tables store the data behind an Interfaces project?

Yes. Zapier describes Tables as an automation-first database solution, and the Form component as collecting information and storing it in Zapier Tables. If you start from a blank form you have to connect a table before submissions have anywhere to go, and Zapier's instructions are explicit that submissions then appear in the connected table, where you can view, filter, search and export them. You can also start the other way round and turn an existing table into a form.

Can I wrap my Interfaces URL in a web view and submit that to the App Store?

You can build it, and Apple has a guideline aimed squarely at it. Guideline 4.2 says your app should include features, content and UI that elevate it beyond a repackaged website, and that an app which is not particularly useful, unique or app-like does not belong on the App Store. Guideline 4.2.2 adds that apart from catalogs, apps should not primarily be marketing materials, advertisements, web clippings, content aggregators or a collection of links. A single web view pointed at a form is the shape both clauses describe. Read from the guidelines dated 16 October 2026.

What happens to my Zaps if I build a real app instead?

They keep working, because the Zap never cared what sent the request. A Zap triggered by a form submission can be triggered just as well by a native screen posting the same fields, and the table behind it does not change. This is the part people expect to lose and do not. What you are replacing is the page, not the automation underneath it.

Does the Stripe component carry over to an app?

Not unchanged, and this is the one to check first. Zapier offers a Stripe component that collects payment for products and services through the project. On iOS, Apple guideline 3.1.1 requires in-app purchase to unlock features or functionality within an app, and forbids using your own mechanism for it. Guideline 3.1.3(e) runs the other way: if people are buying physical goods or services consumed outside the app, you must use a method other than in-app purchase, such as Apple Pay or a card entry. Which clause applies depends on what you are selling, so sort that out before you design the screen.

Who has to submit the app to the App Store?

You do, if the content is yours. Apple guideline 4.2.6 says apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content, and that these services should not submit on behalf of their clients. Any builder that offers to press submit for you is offering a rejection. A builder can hand you the signed build and the TestFlight upload, and the account and the submission stay yours.

Is an embedded Zapier form enough for a phone?

Often, and that is worth saying plainly. A form behind a password that forty people fill in twice a month does not need an install, an app icon or a review cycle. The case for building changes when you need the thing on a home screen, on a phone with no signal, or sending notifications. Those are the three jobs a URL cannot do, and none of them are about the form itself.

Articles · TutorialsUpdated October 2026

Zapier Interfaces does not make a mobile app, and its own documentation never says it does.

There is no export, no build step and no store submission in Zapier Interfaces. What the product hands you at the end is a page at a public URL, plus an embed snippet for dropping that page into another website. Two more things are worth knowing before you plan anything. The product was renamed: Zapier Interfaces is now Zapier Forms, and Zapier says existing projects work exactly the same. And the data behind a project does live in Zapier Tables, which is the piece you get to keep. Every claim about Zapier on this page comes from Zapier's own help centre, read on 22 October 2026. If you landed here because you want the thing on a phone, the honest starting point is build mobile app without coding.

What follows is what Zapier documents the product as producing, what Tables does for you, what Apple says about shipping a wrapped web page, and which parts of your project survive a rebuild. The short answer on that last one surprises people: the Zaps survive.

Start here

The short version

The deliverable is a link, and the automation is the valuable part.

Zapier describes Forms as letting you build forms that collect information and trigger automated workflows. You start a project from a Zapier Copilot prompt, from an existing table, or from a blank form. You add components. You click Share, and you get a URL or an embed. That is the end of the pipeline as Zapier documents it, and it is a reasonable pipeline for an internal tool.

So the migration question is not really about moving a project. It is about which half you are moving. The front of a Zapier project is a web page, and a web page cannot be installed on a phone. The back of it is a table and a set of Zaps, and those sit behind an HTTP request that a native app can make as easily as a browser can. People who plan this well rebuild the front and leave the back alone.

What does Zapier Interfaces actually produce?

A page, at a URL, that anyone with the link can open. Zapier's sharing documentation puts it in one sentence: pages and forms can be shared publicly using the page URL and can be embedded into websites, and by default they are visible to anyone with the public URL. The embed is offered as a script tag or an iframe, with a height, a width, and a toggle for including the page background. You can also restrict which domains are allowed to host the embed, by typing them into an allowed domains field without the protocol or the path.

Access is not all or nothing, which is the feature most people underrate. A project can be open to anyone with the link, locked behind a shared password, or restricted to managed users. Managed users come in two shapes. A one time passcode emails the person a security code the first time they log in. Advanced login lets them in with a magic link or a Google account, and you can approve a whole email domain at once so anybody with an address on it can sign in. Zapier notes that a magic link can only be used once and expires after an hour. You can add a CAPTCHA to either.

The building blocks are components, and the list is short enough to reason about. Zapier documents thirteen: Button, Chatbot, Checklist, Divider, Embed, Form, Kanban, Layout, Link card, Media, Stripe, Table and Text. Several of them read or write a table directly. The Kanban component needs the table to contain at least one dropdown field before it will render a board. The Media component takes images up to 10MB and videos from YouTube, Vimeo or Loom. None of the thirteen produces a file you can install. The word mobile does not appear in the body of any of the four pages used for this section, and neither does iOS, Android, APK or app store.

Zapier Help Centre, create forms in Zapier Forms, read 22 October 2026

Check yours

What your components become on a phone

Tick the components your project uses. The names and the descriptions on the left are the ones in Zapier's own component reference, read on 22 October 2026. The note on the right is what a native rebuild has to answer for.

Nothing ticked. A project built from text, dividers and a single form is the cheapest thing on this page to rebuild, and the one you should think hardest about before you do.

Do Zapier Tables store the data behind it?

Yes, and Zapier is unusually direct about it. Tables is described as an automation-first database solution for storing data and taking action on it. The Form component is described as collecting information and storing it in Zapier Tables. If you begin from a blank form, Zapier tells you that you must connect a table before submissions have anywhere to land, through the Data tab in the form's sidebar, where you either search for an existing table or click Create Table to generate one that matches your fields.

Once connected, submissions appear in that table and you can view, filter, search and export them. Records can also arrive from a Zap rather than a human, and you can import what you already have from a CSV file, Google Sheets or Microsoft Excel, with Zapier creating the fields for you. Fields can enforce a data type. Your account-wide record usage against your plan limit is shown in the bottom right of the table view, which is the number to look at before you assume a table is a database you can grow into.

This is the good news for anyone planning a phone app. The data is not trapped inside a page layout. It is in a named table, with typed fields, reachable by a Zap. A native screen that posts to a webhook can add a record exactly the way the form does, and a native list can read records back out. Nothing about the storage has to be reconsidered because the front end changed. The same reasoning applies to the other tools in this family, which is why appsheet to mobile app lands in the same place from a different starting point.

Zapier Help Centre, connect form to a table, read 22 October 2026

Can you wrap the URL in an app and ship that?

This is the shortcut everybody reaches for, so it is worth knowing what Apple has written about it. Guideline 4.2 says an app should include features, content and UI that elevate it beyond a repackaged website, and that an app which is not particularly useful, unique or app-like does not belong on the App Store. Guideline 4.2.2 says that apart from catalogs, apps should not primarily be marketing materials, advertisements, web clippings, content aggregators or a collection of links. A build whose only screen is a web view pointed at your form is the thing those sentences were written for.

Note what the guideline does not say. It does not ban web views, and plenty of shipped apps contain them. The test it sets is about the app as a whole: whether there is enough of it to be worth installing. A real form screen, a list that works when the lift has no signal, and a notification when a new submission arrives would all count toward that. A frame around someone else's URL does not, and a reviewer can see the difference in under a minute.

There is a second reason the wrapper disappoints people even when it passes. A page loaded over the network needs the network. It cannot send a push notification, it cannot read a barcode without permissions plumbing you have to add anyway, and it holds no state when the connection drops halfway through a submission. Most of the reasons anyone wanted a phone app in the first place live in exactly those gaps.

Apple, App Store Review Guidelines, last updated 16 October 2026, read 22 October 2026

A shared link and an installed app, side by side

The left column is what Zapier documents today. The right column is what an installed build gives you. Read it as a list of the jobs each one can do, rather than a scoreboard, because for a lot of internal work the left column wins on effort alone.

The job	A Zapier Forms page	An app you build and ship
Opens at a URL in any browser	Yes	No
Embeddable in another website	Yes, as a script tag or an iframe	No
Listed on the App Store or Google Play	No	Yes
Sits as an icon on the home screen	No	Yes
Submissions land in Zapier Tables	Yes	Only while you keep the Zap in the path
Access control	Link, password, or managed users with a one time passcode	Your own sign-in, plus whoever you let into the test build
Goes through App Review	No	Yes

What carries over if you rebuild it properly?

The automation does, in full. A Zap does not know or care whether the request came from a browser or from a phone, so the trigger, the table and every downstream action keep working while you replace the screen in front of them. Your field names carry over. Your records carry over, because they never moved. What you are rebuilding is the layout and the interaction, which was always the part a page builder was doing for you.

Two things do not carry over cleanly, and both are worth deciding early. Payments are the first, because the Stripe component is a web payment and a phone is a reviewed platform. Apple guideline 3.1.1 requires in-app purchase for unlocking features or functionality within an app, and forbids your own mechanism for doing it. Guideline 3.1.3(e) points the other way for physical goods or services consumed outside the app, where you must use something other than in-app purchase. Sort out which sentence describes your sale before you draw the screen. The second is the Kanban board, which is a comfortable interaction with a mouse and an awkward one with a thumb.

Newly is an AI app builder for this job. You describe the app in plain English and it writes a real React Native and Expo project you own, with two-way GitHub sync so the code is never somewhere you cannot reach. It uploads iOS builds to TestFlight, publishes to Google Play internal testing and builds a standalone Android APK. It is $25 a month, with no free tier. What it will not do is press submit on the App Store for you, and that is deliberate. Apple guideline 4.2.6 says apps created from a commercialized template or app generation service are rejected unless submitted directly by the provider of the app's content, so the submission is yours to make. The mechanics of that step are in publish to app store.

One honest recommendation to finish. Do not rebuild a form that is working. If forty colleagues open a link twice a month and the submissions land in a table, you have the right tool already, and an install adds a review cycle for nothing. Rebuild when you need the icon on the home screen, the thing to work with no signal, or a notification to arrive without anybody opening a browser. If your starting point is a form rather than a workflow, the same decision from that angle is in jotform to mobile app.

Apple, App Store Review Guidelines, guidelines 3.1.1, 3.1.3(e) and 4.2.6, read 22 October 2026

Questions people ask about Zapier Interfaces and mobile apps

No. Zapier documents the output as a page you share by URL or embed in a website, and nothing else. Its own help centre says a project can be shared publicly using the page URL and can be embedded into websites, with the embed offered as a script tag or an iframe. There is no step that produces an iOS or Android build, no store submission, and no mention of iOS, Android, app stores or native apps in the pages that describe creating, sharing or componentising a project. Checked on 22 October 2026.

Keep the Zaps. Describe the screens.

Write down the fields on your form, the table they land in, and the one thing a page cannot do for you. That list is the brief for the app, and the automation behind it does not have to change at all.

Start building