Verify new contacts

When a contact is created in Customer.io, verify the email with mailfloss.

Try:

See all mailfloss + Customer.io integrations or talk to a human

Trusted by teams already building on Knit·

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.

mailfloss Explore mailfloss →

Triggers

Verification completed

Fires when a list or bulk verification job finishes in mailfloss.

Actions

Verify an email address

Checks whether an email address is valid and deliverable with mailfloss.

Verify a list

Runs a bulk verification on a list of addresses in mailfloss.

Get account credits

Returns the remaining verification credits in mailfloss.

Customer.io Explore Customer.io →

Triggers

New lead captured

Fires when a new lead or contact is captured in Customer.io.

Contact enters a workflow

Fires when a contact enters an automation in Customer.io.

Contact updated

Fires when a field on a contact changes in Customer.io.

Contact unsubscribed

Fires when a contact unsubscribes in Customer.io.

Actions

Create or update a contact

Creates or updates a contact in Customer.io.

Add a contact to a campaign

Adds a contact to a workflow or campaign in Customer.io.

Send a message

Sends an email or message to a contact via Customer.io.

Apply or remove a tag

Changes a contact's tags in Customer.io.

Tag invalid emails When verification completes in mailfloss, tag the contact in Customer.io. See details

Verify before a campaign When a list is created in Customer.io, verify it with mailfloss. See details

See all mailfloss + Customer.io integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Verify new contacts” between mailfloss and Customer.io?

Yes — describe it in the box above and Knit's Integrations Agent researches mailfloss and Customer.io'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 verified?

Yes. When a contact is added in Customer.io, mailfloss can verify the email.

How are invalid contacts handled?

Contacts that fail verification in mailfloss can be tagged or removed from sequences in Customer.io.