HumDay

Send a welcome email from Resend when a contact joins Pipedrive

HumDay can watch Pipedrive for new contacts and send each one a welcome message from your own Resend account. What the email says, which links it carries, and who signs it are part of the contract — the message is the outcome here, so it is agreed before anything is built, and nobody is ever emailed twice.

Build this automation

What this automation is built from

Real operations each provider publishes, in their own words. HumDay only ever uses the specific ones your approved contract needs.

Watching Pipedrive

See all Pipedrive operations

Acting in Resend

See all Resend operations

How this gets built

  1. Describe the outcome. The button above drops this job, already worded, into the composer — edit it until it says exactly what you want.
  2. Approve the contract. Before anything is built you see what it will do in Pipedrive and Resend, what it will never do, and what happens when something fails.
  3. See it proven. The generated program runs and shows you the result — including the duplicate rule working — before it is allowed near either account.
  4. Grant access, then go live. You approve the specific operations it may use on each side — and only those.

Related automations

Questions about this automation

Do I need to write code to send a welcome email from Resend when a contact joins Pipedrive?
No. You describe the job in plain words and HumDay works out which Pipedrive and Resend operations it needs, writes the program, and shows you the result before anything runs live.
What do I need before this can run?
A Pipedrive account and a Resend account. You connect each one when the automation is ready, and you are shown exactly which operations it will use on each side before you grant access.
Will it ever act without my approval?
No. The contract you approve names everything the automation may do, anything that writes to Resend is held behind an approval you grant explicitly, and the generated program cannot reach any service the contract did not name.
How do I know it works before it touches my accounts?
Every automation runs a proof first: the generated program executes against realistic data and shows you the outcome — including what it does with duplicates and failures — before it is allowed near your live Pipedrive or Resend account.
What happens when something fails?
The contract states the failure behaviour up front — what is retried, what stops the run, and when you are told. A failure is reported to you rather than silently swallowed, and the run's evidence shows exactly what happened.

Where this came from

Operations are read from the published API descriptions for Pipedrive and Resend. Descriptions are each provider’s own words, not ours. See everything the Pipedrive and Resend integration can do.