Fetch via Fireround: a company's funding rounds, in the note, in one command
Run one command on a company note and its funding rounds land under Fundraising History, exactly as Fireround returned them.
Why Care?
Funding rounds were only reachable through a folder profile, as frontmatter properties. That's the wrong home for them: a company with a few rounds is thousands of characters of investors and sources, and frontmatter is meant to stay scannable.
Now there's a command, and the data goes in the note.
What's New?
Fetch via Fireround. Writes the company's rounds into the note as a
jsonblock under## Fundraising History, exactly as Fireround returned them. Running it again replaces the block.The same for any data API. A recipe with
write-json-undergets its own Fetch via command, including a recipe file in your vault, with no new release.Only homepages are looked up. A note on
openai.com/sorais about something hosted on that domain, so the host's rounds aren't written to it. A notice says why. This now applies to profile fields too.
Proof
Live on www.firecrawl.dev, through the command's code with a stand-in vault: "wrote 2 records under Fundraising History", above the section's existing text, with the frontmatter untouched. Not yet checked inside Obsidian. Written up for release in 0.2.0.
Under the hood
fetchRecords()is split out ofcallData(): it returns every matching record untouched, andcallData()reads outputs from the first.Fireround's
limitgoes from 5 to 20, since the command writes every round.insertJsonUnderHeading()is copied from Perplexed, since each plugin ships standalone, so a note Perplexed has written is updated in place rather than given a second block.editBody()keeps the YAML out of the heading search.Nothing found leaves the note alone, including a block from an earlier run.
A vault recipe's command appears when recipes are next loaded, and a deleted recipe's command stays until reload, then says the recipe is gone.
8 new tests (183 total).