Skip to main content
Open in Introw: Partners

​
How it works

A partner directory in Introw is not a single button - it is composed from building blocks you already have, so it stays as flexible as your program. The partner data lives in Introw (name, logo, description, location, specialization, tier, and categories), and you assemble a directory from it in whichever shape fits your audience. There are two common shapes, and you can run both:
  • In-portal directory (partner-maintained). A Partner profile smart section shows each logged-in partner their own listing, and a form lets them keep that data current themselves - optionally behind an approval gate or agentic review before changes publish. This keeps listings accurate without your team editing records by hand.
  • Public / external directory (buyer-facing). The partners API (GET /api/v1/partners) returns your partners and their categories, so you render a branded, searchable directory on your own website or marketing site. A dynamic form on that page captures a prospect’s request, auto-attributes the lead to the chosen partner, and kicks off the full suite of Introw automations (routing, notifications, CRM sync, deal or lead registration) behind the submission.
Because both shapes read from live partner records, listings stay current as tiers, segments, categories, and details change - no separate site to hand-maintain.

​
Prerequisites

  • Partners synced into Introw with the details, categories, and tier you want to display. See Sync partners and contacts.
  • Permission to manage partner experiences and forms; an API key with partners:read for a public directory.

​
Settings & configuration

Who appears - scope listings with segments or tiers so only the partners you want to promote show up, and use partner categories as the facets buyers filter by. Partner-maintained data - a form mapped to partner fields lets partners submit and update their own listing; add an approval workflow (human or agentic) so changes are reviewed before they go live. In-portal display - the Partner profile section renders each partner’s own details inside an experience. Public directory + take-in - the partners API lists partners and categories for your own site, and a dynamic form captures buyer interest and auto-attributes it to the partner, triggering your automations.

​
Setup walkthrough

1

Confirm partner data and categories

Make sure the partners, categories, and details you want to show are present in Partners.
2

Let partners maintain their listing

Build a form mapped to the partner fields and (optionally) gate it with approval, so partners keep their own data current.
3

Show it in the portal, publish it externally, or both

Add the Partner profile section to a partner experience, and/or render a public directory from the partners API on your site.
4

Capture and route buyer demand

Put a dynamic take-in form on the directory that auto-attributes each request to the partner and kicks off your Introw automations.

​
How-to guides

Build a partner directory

Assemble a partner directory from Introw’s building blocks: partner-maintained profiles via forms, an in-portal profile section, a public listing from the partners API, and a take-in form that auto-attributes buyer demand to the right partner.

​
Limits & gotchas

A public directory built on the partners API shows only the fields your integration renders, and the API returns only the partners your key is scoped to - sensitive partner data is never exposed unless you choose to surface it. For partner-maintained listings, gate the form with approval if you do not want partner edits to publish immediately.

​
Troubleshooting

  • A partner is missing - check they match your segment/tier scope and have the display fields (and categories) filled in.
  • A listing looks empty - confirm the displayed fields are populated on the partner record, or that the partner submitted the profile form.
  • Filters return nothing - confirm the partner categories (or other filterable fields) you filter on are set on partner records.
  • A buyer request did not reach the partner - confirm the take-in form’s attribution mapping and that the triggered automation is enabled.