Auto-send NetX sales collateral to Slack on HubSpot deal stage change

Build an agent workflow that delivers a tailored kit of approved sales collateral to the deal owner in Slack whenever a HubSpot deal advances into a late-stage pipeline stage (like Proposal, Negotiation, or Contract Sent).

Trigger: a HubSpot webhook for deal property changes. Only fire when the deal's dealstage property changes to a configurable late-stage value, default to 'Proposal'. Ignore all other property changes.

When the webhook fires, do the following:

1. Call HubSpot Get Deal to pull the deal record. Include the deal's industry, product line, deal amount, the associated company (with its industry), and the deal owner.

2. Call NetX Search Assets by Query against the configured 'Approved Sales Collateral' folder or collection. Build the query from the deal's industry, vertical, product line, and any relevant tags. Request asset attributes in the response so the agent can read titles, tags, and the approval-status attribute. If the deal is missing industry or product, fall back to the associated company's industry and the deal name.

3. Filter the results so only assets whose approval-status attribute is approved or active are kept. From those, pick the three to five most relevant assets, mixing formats where possible (one-pagers, case studies, ROI calculators, demo videos). If you need more attribute detail to decide, call NetX Get Asset Attributes on shortlisted assets.

4. For each chosen asset, write a one or two sentence 'why this matters for this deal' blurb that ties the asset to the deal's industry, product, or deal size. Keep the tone direct and useful for a rep prepping a proposal.

5. Call Slack Send a Message to deliver the kit to the deal owner. Default to a direct message, but make the destination configurable so a team can route it to a deal-specific channel or a shared sales-enablement channel instead. The message should include the deal name and the stage transition in the header, then for each asset: the title, a thumbnail preview, the blurb, and a direct NetX share link.

If no assets clear the approval and relevance filter, do not pad the kit. Send a single Slack message that says no strong matches were found for this deal, with the deal name and stage, so the rep knows to browse NetX manually.

Map the HubSpot deal owner to a Slack user so the DM lands with the right person. If the mapping fails, fall back to a configured default channel and note the missing owner in the message.

Additional information

What does this prompt do?

Watches your HubSpot deal pipeline and fires when a deal advances to your late-stage milestone, like Proposal or Contract Sent.
Reads the deal's industry, product line, deal size, and company context, then searches your NetX library for matching approved collateral.
Picks the three to five strongest assets across one-pagers, case studies, ROI calculators, and demo videos, with a short blurb explaining why each fits this deal.
Posts the kit straight to the deal owner in Slack with thumbnails and direct share links, or says so plainly when nothing in the library is a real match.

What do I need to use this?

A HubSpot account with access to your deal pipeline and the deal owner field.
A NetX account with an approved sales collateral folder or collection, and an approval status tag on assets.
A Slack workspace and the channel or direct message where reps should receive the kit.

How can I customize it?

Change which pipeline stage triggers the workflow (Proposal, Negotiation, Contract Sent, or any custom stage).
Adjust the NetX folder or collection the kit pulls from, and the approval status value the workflow filters on.
Swap the delivery target between a direct message to the deal owner, a deal-specific channel, or a shared sales enablement channel.

Frequently asked questions

What if the deal does not have an industry or product set in HubSpot?

The workflow falls back to the associated company's industry and the deal name to guide the search, and tells the rep in Slack when context was thin so they can manually browse NetX.

How does it decide which assets are 'approved'?

It reads the approval status attribute on each NetX asset and only surfaces ones marked approved or active. You define what 'approved' means in your NetX setup, and the workflow respects it.

Will reps get pinged every time anything on the deal changes?

No. The workflow only fires when the deal advances into the pipeline stage you configured. Other property changes are ignored.

What happens when nothing in NetX matches the deal?

The rep gets a single short Slack message saying no strong matches were found, instead of a padded kit of weak picks. The goal is signal, not noise.

Can multiple sales reps share one setup?

Yes. The deal owner is read from HubSpot on each run, so whichever rep owns the deal is the one who gets the Slack message.