Goal
Want signed-in app users to create content from inside the app — a new listing, a classified, a submission, a directory entry? They do it by filling out a form, and you set that up by configuring the Add Item Form on a button’s settings page.
Once it’s set up, the app grows a small Add action — a plus.png button in the screen’s left navigation slot. Tap it, and a Gravity Form you chose opens. Submit that form, and MAM Suite turns it into a new WordPress post. The Post Type and Create status you set here are saved with the screen, but the post’s actual type and publish state also depend on how the form itself is configured — its content type and field mapping — so it’s worth confirming the result once you’ve tested it (Step 7).
This is the no-code path to user-generated content: design the form once in Gravity Forms, point a screen’s Add button at it, and let the platform handle turning each submission into a post.
Prerequisites
- Admin access to Mobile App Manager.
mam-mainactive. The Add Item Form sub-tab ships withmam-main.- Gravity Forms and the MAM Gravity Forms bridge plugin (
mam-gravity-forms-manager) installed and active. The Add Item Form’s Add Form dropdown is populated from your Gravity Forms forms — if the Gravity Forms manager class is not present, the dropdown will be empty and there is nothing to attach. - A Gravity Form already built for the submission you want to collect. Design it in Gravity Forms first, then come back here to attach it.
- A target post type. The post-type dropdown lists every public post type registered on the site (the standard
post, plus any custom post types your source plugins register, such as a listings or directory CPT). Decide in advance which content type a submission should become.
Source-of-truth note: the Add Item Form attaches to a single screen (button), not to the whole app — you configure it per button, and each screen keeps its own Add form, its own post type, and its own publish status.
Steps
1. Open the button you want users to add content from
- Go to Mobile App Manager → App Settings.
- Open the screen (button) where you want the Add action to appear. Screens show up as the horizontal tabs across the top of the App Settings page (for example, Left – Listings) — usually you’ll pick a list or feed screen, since that’s where the new items will show up once they’re created.
- On the button’s settings page, click the Add Item Form sub-tab, which sits alongside the other per-screen sub-tabs: General Settings, Layout Settings, Content Sections, and — where applicable — Tab Bar Manager.
2. Choose the form
In the Add Form dropdown, pick the Gravity Form your users will fill out to create an item — the dropdown lists your Gravity Forms forms by title.
An empty dropdown means the Gravity Forms bridge isn’t active, or you don’t have any forms yet — see Prerequisites.
3. Choose the create status
The Create status radio decides what happens to a submission the instant it’s created:
| Option | What it does |
|---|---|
| Published | The new post goes live immediately. Use this when you trust submitters and want their content to appear in the app right away. |
| In Review | Your intended state when moderation is wanted — the post should be held and not appear publicly until you approve it. Exactly how a submission is held depends on the form and post type in use, so verify the hold behavior before relying on it for moderation. |
If any app user can submit, choose In Review — you don’t want unmoderated content going live on its own. Save Published for submitters you already trust (a staff or vendor role, say) or for setups where you have other moderation in place. Either way, confirm the hold actually happens in your app before you rely on it (Step 7).
4. Confirm the post type
In the Post Type dropdown, select the content type a submission should become — the list contains every public post type on the site.
Think of this as declaring your intent: if users are adding listings, pick your listings post type; if they’re adding blog-style posts, pick post; and so on. Just make sure it lines up with the Gravity Form behind the screen — the form’s own configured content type and field mapping (title, body, and any meta the post type expects) is what actually governs the post that gets created, so the two should be describing the same thing.
5. Note the icon
The Icon here is fixed to plus.png, the standard “add” plus symbol — there’s nothing to choose, it’s just shown so you know which control is about to appear in the app. In the app it becomes the screen’s left-side Add action, titled “Add”.
6. Save
Submit the form on the Add Item Form sub-tab. Your settings are stored per button (and per account), and the screen’s data payload — the bundle of data the app downloads from your site — is refreshed so the next app fetch includes the new Add action.
7. Verify in the app / Previewer
- Open the Previewer (or a real device) as a signed-in user who has access to the screen you configured.
- Open that screen — you should see an Add (plus) action in the top-left navigation slot.
- Tap it. The Gravity Form you selected should open.
- Fill it out and submit — a new post of your chosen post type should get created.
- Check the status:
- If you chose Published, the new item should show up in the app’s list for that content type.
- If you chose In Review, it should not appear publicly yet — confirm it’s sitting in WordPress admin awaiting approval, then approve it and check that it now appears in the app.
If the Add button never shows up:
- Make sure a form is actually selected in Add Form — leave it blank and no Add action gets emitted at all.
- Check that Gravity Forms and the MAM Gravity Forms bridge are both active.
- Re-save the Add Item Form sub-tab and re-fetch the app data.
If submitting doesn’t create a post:
- Check that Post Type is set, and that your Gravity Form actually maps its fields to that post type.
- Confirm the submitter’s role has permission to reach the screen and submit.
How it fits together
| Piece | Owned by | Role |
|---|---|---|
| Add Item Form sub-tab | mam-main (per-button settings) |
Where you attach a form, status, and post type to a screen. |
| Add Form dropdown | Gravity Forms via mam-gravity-forms-manager |
The list of forms you can attach. |
| The Add (plus) action in the app | mam-main local settings |
Rendered into the screen’s left-nav slot when a form is attached; opens the form. |
| Post creation on submit | Gravity Forms + MAM bridge | Turns the submission into a WordPress post, based on the form’s configured content type and field mapping. |
The form itself — its fields, validation, confirmation, and any conditional logic — lives entirely in Gravity Forms. The Add Item Form sub-tab’s job is simpler: it decides which form a screen offers, and records the post type and create status you intend for that screen.
Related
- Plugin: mam-contact-form — a related Gravity-Forms-backed form path, for a Contact Us form rather than content creation.
- Recipe: Add a button — the general per-screen settings workflow this builds on.
- Building Your App: navigation and tab bar — for where the screen with the Add button lives in app navigation.
- Gravity Forms in MAM Suite — designing the form that backs the Add action.
