Update segments
When a contact is enriched in Clearbit, update fields on the contact in Metadata.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Metadata Explore Metadata →
TriggersFires when a new lead or contact is captured in Metadata.
Fires when a contact enters an automation in Metadata.
Fires when a field on a contact changes in Metadata.
Fires when a contact unsubscribes in Metadata.
Creates or updates a contact in Metadata.
Adds a contact to a workflow or campaign in Metadata.
Sends an email or message to a contact via Metadata.
Changes a contact's tags in Metadata.
Clearbit Explore Clearbit →
TriggersFires when Clearbit finds or captures a new lead.
Fires when a new contact is added to a list in Clearbit.
Fires when a new company matches a saved search in Clearbit.
Adds job title, phone and company data to a contact with Clearbit.
Looks up firmographic data for a company with Clearbit.
Finds and verifies a prospect's work email with Clearbit.
More Metadata + Clearbit workflows
See all Metadata + Clearbit integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Update segments” between Metadata and Clearbit?
Yes — describe it in the box above and Knit's Integrations Agent researches Metadata and Clearbit's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Can new contacts be enriched?
Yes. When a contact is added in Metadata, Clearbit can add company, industry and role.
Can prospects join campaigns?
Contacts found in Clearbit can be added to lists or sequences in Metadata.