Skip to main content

Customer pre-meeting summary

Builds a short customer brief from the company page, so a sales rep walks into a meeting knowing who the buyers are and what the customer ordered lately.

Runs: Embedded in Propeller · Trigger: Button · Difficulty: Easy

What you need​

  • An n8n account. See Set up n8n.
  • A Propeller API key.
  • Owner access on the Configuration role to create the agent.

How it works​

When you run the agent on a company page, the workflow takes the company from the page and gathers:

  • Buying team: every contact with a purchase authorization for the company, with their role. For a purchaser it shows the amount they can order without approval.
  • Activity: the number of orders in the last 90 days and the number of quotes, with totals, the statuses by name and the last order. Which statuses count as orders and as quotes is set in Settings.
  • Quotes by date: how many quotes are valid today or have no date, and how many have a Valid Until date in the past, with their totals.
  • Top products: the three products with the most revenue in the latest 20 orders.

The brief comes back as a message in the agent panel.

Install it​

  1. In n8n, import the downloaded JSON as a new workflow.
  2. On the Webhook node, set a basic auth credential (a username and password you choose) and copy the production URL.
  3. Create a header auth credential with your Propeller API key and select it on the Fetch Brief node.
  4. Activate the workflow.
  5. Go to Admin > Agents and create an agent with Trigger Button and Interaction Mode Single Turn. Under Types, pick SALES_HUB_COMPANY. Paste the webhook URL and the same basic auth values. See AI Agents.
  6. Open a company, click the Workflows button and run the agent to test it.
Filling in your API key

In n8n, create a credential of type Header Auth and fill in its two fields exactly like this:

FieldWhat to fill in
NameapiKey
ValueYour Propeller API key

Name is not a title you pick yourself. It has to say exactly apiKey, otherwise the workflow cannot sign in. See Set up n8n for the full steps.

Placement matters

An agent type is the page where the agent appears. Stick to the types listed in the install steps: the workflow depends on the data that page sends along, so placing the agent on other pages may not work.

Make it yours​

  • Lookback window: ACTIVITY_DAYS in the Settings node (default 90).
  • What counts as an order and as a quote: ORDER_STATUSES and QUOTE_STATUSES in Settings (defaults as in the earlier version). Which statuses to include depends on how your team uses order statuses.
  • Top products: LINES_FROM_LAST and TOP_PRODUCTS in Settings.
  • Brief content: the sections live in the Format Brief node.

Limits​

Counts are exact for any account size. Totals are summed over the latest 50 orders and the latest 50 quotes; the brief says so when there are more. The workflow reads few orders on purpose: a large order takes longer to read, and the agent waits 30 seconds for an answer by default.

Use it outside n8n​

Copy the JSON into an AI assistant and follow Adjust a workflow with an AI assistant.

Good to know

The workflows and agents in the Agent Hub are free to use and adapt. They are examples, not supported product features, so test them in a staging environment and check the results before using them in production.