Find missing addresses
When a contact lacks an email, find one with Clay and send the email from GMass.
4.9/5 on G2·
Google for Startups Accelerator
How 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.
GMass Explore GMass →
TriggersFires when a new email arrives in GMass.
Fires when an email is sent from GMass.
Fires when a tracked email sent via GMass is opened.
Fires when an email sent via GMass bounces.
Sends an email via GMass.
Creates a draft email in GMass.
Applies a label or folder to an email in GMass.
Moves an email into a different folder in GMass.
Clay Explore Clay →
TriggersFires when Clay finds or captures a new lead.
Fires when a new contact is added to a list in Clay.
Fires when a new company matches a saved search in Clay.
Adds job title, phone and company data to a contact with Clay.
Looks up firmographic data for a company with Clay.
Finds and verifies a prospect's work email with Clay.
More GMass + Clay workflows
See all GMass + Clay integrations → · Browse the full workflow library →
Common questions
Can Knit build “Find missing addresses” between GMass and Clay?
Yes — describe it in the box above and Knit's Integrations Agent researches GMass and Clay'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 email senders be enriched?
Yes. When a new email arrives in GMass, Clay can enrich the sender with company and role.
Can Clay find emails for outreach?
Contacts found in Clay can receive emails sent through GMass.