App Market

Bundle one or more tables (with their views, reports, web forms, and flows) into a template, then publish it for other InfoLobby users to install in one click. Other users install your template into their own workspace, modify it as much as they want, and start from it instead of a blank table.

InfoLobby distinguishes two kinds, derived automatically from how many tables you bundle:

• App Template: a bundle of exactly one table.
• Workspace Template: a bundle of two or more tables (closer to a full workspace setup).

You don't pick the type; the label flips automatically as you tick tables when publishing.

Record data is never shared. Templates are schema only.

Browse and install

Open the user menu in the header and choose App Market, or go to /app-market.

1. Pick a template from the hub. The card shows whether it's an App Template or a Workspace Template.
2. The detail page shows the publisher, what tables come with it, a preview of each, and a Requires panel listing any connections the template's automations need.
3. Click Install Template. If you are logged out, you log in first and come back.
4. Choose a default workspace: create new, or pick an existing one.
   • If the template spans several workspaces, you instead name each one. They are all created fresh, because there is no single existing workspace a multi-workspace bundle could merge into.
5. For each table in the template, choose a destination:
   • (use default): goes to the default workspace.
   • Create new in <workspace>: different tables can land in different workspaces.
   • Use existing: <table>: merge into a table you already have. Lookups between template tables will rewire to it.
6. If the template references tables not included in it (external lookups), pick a target table for each.
7. Resolve the Requirements section (see below).
8. Click Install.

Whether each flow ships with the template is decided by the publisher. There is nothing to choose for flows at install time.

Requirements (connections)

A template's automations may need a connection of yours: an SMTP server to send email, an OpenAI key, an API connection. A table with record email enabled needs an SMTP server too.

Templates never carry the publisher's credentials, and never carry their server addresses or usernames either. Only the type of connection needed travels, plus the provider brand where the publisher used one.

The install modal lists each requirement and what uses it. For each one, pick one of your own connections of the right type, or click Set up a new one… to create one in a new tab and then Recheck. Install stays disabled until every requirement is resolved, so you never end up with automations that look installed and quietly fail.

Setting up a new connection is offered even when you already have one of the right type, in case you would rather the installed automations run through their own.

You'll see installed templates in Account → App Templates → Installed Templates.

Publish a template

Open Account → App Templates and click Create New Template.

Uninstall

In Account → App Templates → Installed Templates, click the Forget icon to remove an install record from your list. Your tables and data are not touched. If you also want to remove the tables, delete them from each workspace using the standard table-delete flow.

What gets installed

Connections the template needs are resolved during install (see Requirements above), so imported flows point at your own connections from the moment they land.

Notes

• Each install creates a new row in your installed-templates list, even if you re-install the same template.
• Install count is shown on each public template card.
• Cross-workspace templates are supported: a single Workspace Template can bundle tables from any of your workspaces. When the bundle spans more than one workspace, installing it recreates that structure rather than flattening it into one.