MARKET RESEARCH
On-Demand Filing Diff Memo Published to Confluence
On a webhook trigger with a company and filing URL, fetches the document, diffs it against the prior filing.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives company + filing URLHTTP webhook
- ActionBrave Search finds prior comparable filingBrave Search
- ActionFetch new and prior filing textOpenAI
- ActionOpenAI builds structured diff memoOpenAI
- OutputPublish versioned memo to ConfluenceConfluence
What it does
When an analyst submits a company and a filing URL, this workflow pulls the new document, retrieves the prior comparable filing via Brave Search, and produces a section-by-section diff memo highlighting changed risk factors, restated numbers, and new disclosures. The finished memo is published as a versioned Confluence page in the coverage team's research space.
When to use it
Use it when an analyst spots a fresh filing and wants a clean, shareable diff memo in the team wiki rather than a throwaway Slack message. It is ideal for building a durable, searchable archive of what changed and when across covered names.
How it works
- 1A webhook receives the company name and the new filing URL.
- 2Brave Search locates the prior comparable filing for the same issuer and filing type.
- 3An action fetches both the new and prior filing text.
- 4OpenAI generates a structured diff: changed risk factors, restated figures, new line items, and a plain-English so-what.
- 5The memo is published to Confluence as a new page under the issuer's folder, preserving page history for audit.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect Brave SearchWeb, news, image, video search.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect ConfluenceSpaces, pages, blueprints.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Market Research workflows
Enrich Inbound Accounts with BigQuery Firmographics and Score Fit
When a new account row lands in Airtable, joins it against BigQuery public business datasets to attach firmographic attributes.
Blend BigQuery TAM with Live Competitor Signals into a Notion Brief
On demand, sizes a chosen segment from BigQuery public data, gathers current competitor signals via Brave Search, and synthesizes a one-page market brief into Notion.
Allocate Sales Territory TAM from BigQuery Geo Data to HubSpot
When triggered by a webhook, queries BigQuery public ZIP-level business data to compute TAM per sales territory.
Hiring Surge Detector with Slack Alert
Detects when a target account's open-role count jumps above its recent baseline and posts a ranked Slack alert to the GTM channel so reps can act on a company that is clearly…
Tech-Stack Shift Inference from Job Descriptions
Reads new job descriptions for target accounts, uses an LLM to extract named technologies and infer stack changes.
Weekly Hiring-Intel Briefing for GTM
An agent reviews the week's accumulated hiring signals across all target accounts, writes a narrative briefing that infers each account's likely initiatives.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.