Prospecting
Forager
Job postings, company firmographics and contact enrichment, billed per lookup.
Official site: forager.ai
What it does
- Search job postings by company, title, location or remote status
- Search organizations by industry, headcount or the technologies they run
- Enrich a person — work emails, personal emails, phone numbers
- Read a domain's technology stack, and check the credit balance
Two things shape how a workflow should call this. Every search and every lookup spends a credit, so asking for the count first and the page second is the difference between a cheap question and an expensive one. And the filters take numeric ids, never free text: locations: ["Paris"] matches nothing at all until Paris has been resolved to its id, and it fails by returning an empty result rather than an error.
Why through Tulina
Most systems now publish their own way for a model to reach them, and that is a good thing — it is what Tulina connects to. The connection was never the hard part. Deciding who may use it, what it is allowed to return, and what the model knows before it asks: that is.
The keys stay in one place
Connect Forager once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that — so nobody is blocked and nobody is handed more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
Roles decide who can reach Forager at all. Beyond that, a policy on the connector itself decides what comes back: fields dropped, identifiers masked or hashed, people pseudonymised. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
Runs are logged for the organisation — what was called, by whom, when. That is what makes an automated action reviewable after the fact, and what a security review asks for first.
The run starts knowing your company
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Forager returns something usable instead of something generic.
Processes that run on Forager
None published yet.