Use a Notion public form as an opportunity inbox

Use one form as the opportunity inbox

A public Notion form can turn incoming suggestions into database records that a person or small team can review, filter, assign, and follow up. Notion forms connect each question to a property in the connected database, so the form and the response records share one structure. Notion's Forms documentation describes the product behaviour; the opportunity-inbox pattern is the design recommendation here.

The minimum workflow is:

This is a collection and review system, not a promise that every lead is good or that every submission will be handled immediately. The form makes incoming context easier to inspect; the decision still belongs to the person responsible for triage.

• A scout, partner, student, colleague, or other contributor opens one form link.
• They submit the opportunity details they know.
• Notion creates a record in the connected database.
• A human reviews the record and assigns a stage, owner, priority, and next action.
• Triage views surface the work by deadline, type, owner, or follow-up date.

Separate public intake from internal triage

The most important design choice is to use two layers in one database. Public questions should help a contributor explain the opportunity. Internal properties should help the team decide what happens next. Do not ask an outside contributor to set your priority or mark an opportunity as shortlisted; those fields represent an internal judgment they may not be able to make.

Start with this small public field set:

Add these internal properties after the form is working:

This separation keeps the public form short and makes the database useful after submission. It also reduces the temptation to build a full CRM before you know which decisions the inbox must support.

• Opportunity title.
• Source URL.
• Opportunity type, such as grant, partnership, job, procurement, event, or project.
• Deadline, if one is known.
• Eligibility, location, or other practical constraint.
• Why it may be relevant.
• Submitter context or an optional way to follow up, if your process needs it.
• Stage: `New`, `Needs review`, `Shortlisted`, `Not a fit`, or `Closed`.
• Owner: the person accountable for the next review or response.
• Priority: a small scale such as `High`, `Normal`, and `Low`.
• Next action: the concrete step needed to assess or pursue the lead.
• Review date: when someone will look at it again.
• Fit assessment and decision notes.

Build the public form around contributor knowledge

Create the form in the page where you want the inbox to live, or add a Form view to an existing database. Notion says that creating a form from an existing database requires `Full access` to that database, and that editing the form requires `Can edit` or `Full access`. Check the current Forms instructions for the interface and permission details.

Use questions that a contributor can answer without understanding your internal workflow. A short title and source link make the record findable. A type selector gives you a reliable filter later. A deadline field preserves time-sensitive information without making the contributor write it into a paragraph. The relevance question captures the reasoning that would otherwise disappear in a forwarded message.

Make only the fields necessary for a useful first review required. Explain what belongs in each field, especially for a source URL or deadline. If an opportunity has no known deadline, allow the contributor to say that rather than encouraging a guessed date. Avoid collecting confidential documents, sensitive personal data, or information you do not need to decide whether the lead deserves attention.

The form should be a doorway into the inbox, not the inbox itself. Keep internal notes, fit judgments, ownership, and follow-up out of the public questions even when the connected database contains those properties.

Create views for the decisions you actually make

The database is the working record; views are different ways to review it. Begin with a few views that answer real triage questions:

For a concrete first view, map `Opportunity title`, `Opportunity type`, `Deadline`, and `Why it may be relevant` from the form, then show those fields alongside the internal `Stage`, `Owner`, and `Next action`. Filter the view to known deadlines that are not `Closed`, sort by the earliest deadline, and group by opportunity type. A reviewer can then decide what to inspect next without opening every long intake response.

Keep the source URL, deadline, owner, stage, and next action visible in the review views. Hide long intake explanations only when doing so helps the reviewer scan; do not remove the context needed to make a responsible decision. A filtered view should reduce noise, not replace a clear stage definition or a named owner.

Use the first review to turn an unprocessed record into a decision-ready one. Confirm that the source is relevant, check the deadline against the source itself, choose a stage, assign an owner, and write the next action. If the lead is not a fit, record that plainly so the same suggestion does not keep returning to the inbox.

• New submissions: `Stage` is `New`, sorted by creation date.
• Upcoming deadlines: a known deadline is near, with the stage visible.
• By opportunity type: grouped by grant, partnership, job, procurement, event, or project.
• Assigned to me: the current owner is the person reviewing the view.
• Follow-up due: the review date or next action is due.

Share the link with clear limits

In the form's sharing settings, `Anyone on the web with link` allows people outside the workspace, including people who do not use Notion, to fill it out if they have the link. That setting does not mean the form is automatically discoverable; treat the link as the route people need. Notion documents the available sharing options, including the ability to close a form by setting it to `No access`.

Web submissions are automatically anonymous in Notion's form settings. In practical terms, do not assume that a respondent's Notion identity will be captured for you. If follow-up matters, ask for a contact method as an explicit form question. Anonymous also does not mean private, trustworthy, or abuse-proof: a public link can be forwarded, and submitted text still needs human review. Do not use the form as a place for confidential information merely because the respondent's name is not recorded.

There are product limits to account for before you share widely:

These are reasons to test the sharing and duplication path before presenting the setup as reusable. This article describes a workflow pattern, not a downloadable or independently tested Notion asset.

• Conditional logic, which changes the questions shown based on an answer, is available only on Business and Enterprise plans.
• Notion notes that a very high volume of responses can make a form slower to load.
• A Form view cannot currently be exported directly. Notion recommends exporting the questions and responses from a Table view instead.
• To view responses, a workspace member needs at least `Can view` access to the connected database; editing responses requires the relevant edit access.
• If you later package the workflow for duplication, create a separate form version from scratch so responses route to the new owner's database rather than the original creator's form.

Add automation only after the inbox works

The basic workflow does not require AI. First make sure a new response arrives with understandable fields and that a human knows who will review it. Extra automation is useful only when it removes a repeated handoff without hiding an important judgment.

Notion forms can trigger actions after a response, such as sending a notification. Buttons can later help someone change a status, add a page, edit properties, or send a notification, but Notion says some button actions are paid-plan features and that the person creating or editing the button needs the relevant page permissions. See the current Buttons documentation before relying on a particular action.

Database automations can respond to events such as a page being added or a property changing. Notion says they are generally available on paid plans and require full access to create, edit, or delete them; Free Plan users can create Slack notification automations but no other kinds, and can use existing automations in templates without editing them. Automations also will not act on pages whose access is restricted. The Database automations guide lists the current triggers, actions, and limitations.

AI is optional and should not silently decide whether an opportunity is worth pursuing. Notion's Basic Autofill can summarize, extract, translate, or categorize from the specific row or page, but it does not browse the web. Custom Agent Autofill can use web search when enabled, uses credits, and still needs verification before its output is relied on. Notion's AI for databases documentation is the source for those current distinctions.

Validate the inbox before sharing it

Run a small test from the contributor's point of view before you distribute the link:

If those checks pass, share the one link with the people who are most likely to send useful leads. Keep the form short, review the inbox on a named rhythm, and add automation only when the repeated work is clear. The reliable part of the pattern is not the form alone; it is the handoff from structured intake to accountable human judgment.

• Submit a realistic opportunity using the public link while signed out or outside the workspace, where the form's sharing setting permits it.
• Confirm that the response becomes one record in the intended database.
• Check that the source URL, type, deadline, and relevance explanation land in the expected properties.
• Confirm that internal stage, owner, priority, next action, and decision notes remain part of the triage workflow rather than public questions.
• Open each triage view and verify that the test record appears where its stage, type, deadline, owner, and review date predict.
• Decide who reviews `New` records and how often the follow-up view is checked.
• If you later package the workflow for duplication, repeat the test in the duplicated workspace and verify that its form points to its new database.