Skip to main content
Every step between a partner’s idea for an activity and the proposal landing against the fund costs you participation. Configure the proposal form once, then let partners propose through whichever entry point fits how they work - a link, an embed, email, Slack, Teams, their AI assistant, or a call from their own systems. Every channel feeds the same form, so the request always lands attributed to the partner against the right fund.
You configure one proposal form - with its CRM automation, partner attribution, and approval - and then expose it through as many channels as you like. This guide covers each one. Pick the channels where your partners already are; you don’t need all of them.

Before you start

1

Configure the proposal step

A fund with its proposal form must exist, and every channel below feeds it. Set it up in Configure the proposal step, which also covers attribution and approval.

Choose a channel

Many partners arrive on pages you already own - a partner marketing page or portal. Embedding the proposal form there lets a partner propose in context, with your branding, without leaving the page. Where the page is partner-specific, use an attributed embed so each submission credits the right partner. Embedding requires a custom domain; without one, share the link instead.
1

Open the share dialog

In Forms, open your form and open its Share form dialog.
2

Switch to the Embed tab

On the Embed tab, copy the generated HTML snippet.
3

Paste it on your page

Add the snippet to the page where you want partners to , such as a partner landing page or a website footer.
4

Attribute where possible

Where you know the partner, use an attributed embed so each submission credits the right partner instead of arriving anonymous.
A partner often thinks of an activity to fund mid email thread. Letting them email the details captures the moment: the AI agent reads the forwarded message and fills in the proposal form for them, so it still lands attributed and against the right fund. The AI agent must be enabled for your program.
1

Set up the partner support email

Confirm your partner support email address is active. Partners forward a lead to it, and the AI agent reads the email and submits the for them.
2

Tell partners they can email

Share the address and a short note that they can forward a prospect with a sentence of context to a deal, no portal needed.
3

Let the agent fill the form

The agent maps the email into your form, so the deal still lands attributed and CRM-ready.
If your partners live in Slack, bringing the Introw agent into the channel lets them propose in the same place they already talk to your team. Connect your workspace first - see Connect Slack.
1

Connect Slack

Connect your Slack workspace so the Introw agent can take s from chat. See Connect Slack.
2

Bring the agent into a channel

Add the Introw agent to the partner channel where deals come up.
3

Let partners submit from a message

Partners give the agent the deal details in a message, and it submits the through the same form flow so they can without leaving Slack.
Same as Slack, for Teams-first channels. Connect your tenant first - see Connect Microsoft Teams.
1

Connect Microsoft Teams

Connect your Teams tenant so the Introw agent can take s from chat. See Connect Microsoft Teams.
2

Bring the agent into a channel

Add the Introw agent to the partner channel where deals come up.
3

Let partners submit from a message

Partners give the agent the deal details in a message, and it submits the through the same form flow so they can without leaving Teams.
When a partner already works in an AI assistant, the lowest-friction path is to just ask it. An assistant connected to Introw over MCP fills in the proposal form and submits it, attributed to the partner, without switching tools. See Connect an MCP client and, for partners running their own assistant, Partner Connect.
1

Enable the AI agent

The AI agent powers assistant submissions. Confirm it is enabled for your program.
2

Connect an AI assistant

Where partners use an AI assistant connected to Introw through the MCP server, they can ask it to a deal in plain language.
3

Share an example prompt

Give partners a short example prompt so they know they can a deal straight from their assistant, which calls the same form flow.
When a partner plans campaigns in their own marketing tooling, the proposal can start there instead of in a form. The API submits the same proposal form from anywhere, with no browser and no login, so their system, your tooling, or an agent files the request. It lands attributed to the partner you name, against the right fund, and follows the same approval flow. See Submit a form via the API.
1

Create an API key with Forms - Write

In API keys, create a key with the Forms - Write permission and copy the secret once. Add Forms - Read if your code should also fetch the form’s field schema. See Create and manage API keys.
2

Copy the request from the API tab

In Forms, open your form, open Share form, and switch to the API tab. The cURL snippet there already carries this form’s id and every field id, and the Fields table below it marks which ones are required.
3

Post it from your own system

Call the endpoint from your product, your internal tooling, a script, or an agent. Send partnerId so the is attributed to the right partner, and Introw runs the same automation, checks, and approval flow as a partner filling in the form. See Submit a form via the API.

Verify it worked

Use whichever channel you set up to submit a test proposal, then confirm it appears in Submissions under Form submissions, attributed to the right partner, against the correct fund.

Configure the proposal step

Build the form, attribution, and approval behind every channel.

Run the MDF lifecycle

Review and process the proposals that come in.

Connect an MCP client

Let assistants propose through Introw’s MCP server.

Submit a form via the API

Let a partner’s own system, your tooling, or an agent propose headlessly.

Implementation reference

Full proposal and submission configuration options.