MARKET RESEARCH
Capture a license baseline when a new model is added to the watchlist
When an operator adds a new model to the Coda watchlist, fetches its current HuggingFace license and metadata and records a signed baseline row so future change-detection has…
How it runs
The automated pipeline, trigger to output.
- TriggerNew model row added to Coda watchlistCoda
- ActionFetch license + metadata from HuggingFaceHugging Face
- LogicVerify model exists and license is present
- OutputWrite confirmed baseline back to Coda rowCoda
What it does
Establishes the "day zero" license record for any model you start depending on. The moment someone adds a HuggingFace model ID to the Coda watchlist, this workflow fetches the current license, model author, and last-modified date and writes a baseline row. Every later scan compares against this captured baseline, so a change is never missed because there was no prior value.
When to use it
Use it as the intake half of a license-watch program. Run it alongside a daily scan: this one handles onboarding new models cleanly, the scan handles ongoing drift. Especially useful when many engineers add models and you need a consistent, automatic baseline rather than relying on manual entry.
How it works
A Coda row-added event on the watchlist table fires the flow with the new model ID. It calls HuggingFace to fetch the model card license, author, and last-modified timestamp. A logic step verifies the model exists and the license field is present; if the model is missing or private it marks the row as needs-review. Otherwise it writes the captured license and metadata back into the same Coda row as the confirmed baseline and stamps the onboarding date.
Set it up
What you configure once, before turning it on.
- 1Connect CodaDocs, packs, automations.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.