Forms
Collect emails in the DM, not on a landing page
Your automation sends the link, they tap it, and most of them meet a page built for desktop traffic. Forms give that person one question on one screen instead. Answers come back to you, and a thank-you DM goes back to them.
See it run
Your DM carries a form link instead of a landing page.
How it works
Build the form
Add fields, pick a type for each one, mark what is required. Email, phone, number, date, dropdown, checkbox and long text are all there, and the type handles validation for you.
Attach it to a DM
In the Builder, add a link button and pick your form from the dropdown. The public link fills itself in. Carousel cards work the same way, so one DM can offer two different forms.
Read the answers
Entries land under the form as they come in. Scan the table, expand a row for the full response, export the lot to CSV when you want it in your email tool.
The thank-you DM
When someone taps a form link from your DM, the link quietly carries who they are. Submit the form and we can match it back, so a reply can go out automatically: "Got it, thanks. Sending your guide now."
Two limits worth knowing before you rely on it. It only fires for people who arrived through a DM link, because that is the only case where we know who submitted. And it respects Instagram's 24-hour messaging window, so a submission that arrives three days later is saved without a DM rather than risking your account.
What people use it for
Waitlists
One email field and a dropdown for which product they want first. People fill it in without leaving the conversation.
Booking enquiries
Name, email, preferred date. You sort the rest in the reply instead of making them fill in a brief.
Discount claims
Email plus a marketing checkbox, so the list you build is one you can actually send to.
Post-launch feedback
A single long-text question. People write more than you would expect when there is only one box on the page.
Where the answers go
Entries live in the app, and you can also push every one of them somewhere else the second it arrives. Send them to Google Sheets as a new row, matched to your own column names, or post them to your own endpoint as signed JSON. Both can run on the same form.
Privacy
Form pages are never indexed. They carry noindex headers, sit behind a random link that cannot be guessed from your form title, and are blocked in robots.txt. Anyone with the link can open the form, which is the point of sharing it, so treat the link as shareable rather than secret.
Pairs with documents
Forms collect an answer. Documents deliver one. A carousel DM can send both: the guide on one card, the waitlist form on the next.
Connect your accountAsk for it
Need something that is not here yet?
Tell us what you were hoping to find. Requests from people who are still deciding are the ones that shape what gets built next, and they go straight to the person who writes the code. Leave an email and you get an answer, not a silent roadmap.
Bigger idea, or a build of your own? The full request page has more room.