ITISYOUVerify

Independent verification of one automation

Know whether your automation actually did the job.

A workflow that runs without an error is not the same as a workflow that produced the right result. We check the second thing, by reading HubSpot and Resend back ourselves.

£29.00 a month · 500 runs · one workflow · HubSpot and Resend

Synthetic example enq_0000000000000001

What the automation reported

contact
created
ack email
sent to a**@example.test
http
200, workflow completed

What we retrieved ourselves

contact
crm-rec-1, created 30s after the enquiry
ack email
a**@example.test, status bounced
read at
2026-09-20 11:50 UTC
Status: Failed

The contact exists and carries the right correlation value. The acknowledgement did not reach the address the enquiry named, so this run failed.

  • The CRM record exists read back from HubSpot, not from the automation report met
  • It carries the enquiry correlation value verify_correlation_id = enq_0000000000000001 met
  • The acknowledgement reached the recipient Resend message outcome: bounced not met

A synthetic example. The same record, read back from HubSpot and Resend, is what decides the verdict, not the automation own report.

Four results, never a fifth

What we report

Your automation says it worked. We read the CRM record and the email outcome back from HubSpot and Resend ourselves, and tell you what the evidence actually shows.

Status: Verified

Every check you set as mandatory has enough supporting evidence from HubSpot and Resend.

Status: Failed

The evidence contradicts one of your mandatory checks, or the completion deadline passed while we could still reach both providers.

Status: Unverified

We could not get a clear answer: access, correlation or evidence was missing or ambiguous. This is not a pass and not a failure.

Status: Pending

Still inside the agreed completion window. We are still checking.

Read this before you buy

What this does not do

It does not watch your automation platform

We never see inside n8n, Make, Zapier or whatever runs your workflow. We only see what exists in HubSpot and Resend afterwards, so we cannot tell you which step of your automation went wrong.

It does not fix anything

We do not create or edit CRM records, and we do not send a replacement email. We report what we find; your team still does the fixing.

It does not cover every workflow

Version one checks exactly one shape: an enquiry that should create the correct CRM record and trigger an acknowledgement email, using HubSpot and Resend only.

It does not detect a run that never started

We only learn about an enquiry when your automation sends us an event. We cannot tell you that a run never started, because we have built no way to find enquiries your automation never reported. If it stops calling us we show nothing, not a pass, not a failure, and every result names the coverage we actually have.

It is not instant

Results depend on a scheduled check, not a live push. A result can take up to an hour to settle.

Three steps

What setting this up actually involves

  1. Connect HubSpot and Resend

    Give us read access to your HubSpot contacts and to the Resend account your acknowledgement emails go through. We never ask for write access, and we never fetch a URL you supply: only the two connected providers.

    What we ask for

    • hubspot crm.objects.contacts.read
    • resend read message outcomes
    • write never requested
  2. Define the expected result

    Tell us which HubSpot property carries your correlation value, and set the checks that must be true: the record exists with the right value, the email reached the right recipient, the status reached the point you need. Your automation sends us one signed message per enquiry naming what it expects: that message is a trigger, never proof on its own.

    One signed event per enquiry

    • event_id one per enquiry, counted once
    • correlation_id the value on the CRM record
    • expected crm_record_id, email_message_id,
    • email_recipient
  3. Receive the evidence

    We read the record and the email status back ourselves and tell you verified, failed, unverified or pending, with the reason for each check and the evidence attached. No fifth status, no silent guessing.

    What comes back

    • status VERIFIED | FAILED | UNVERIFIED | PENDING
    • checks each one met, not met, or not checked
    • evidence what we read, and when we read it

What do I need before I can start?

A HubSpot account you can grant us read access to, a property on your HubSpot contact records that carries a correlation value for each enquiry, a Resend account whose message events we can read, and a small change to your existing automation so it sends us one signed event per enquiry. This is real setup work, not a one-click connection. There is no separate onboarding guide yet: the how-it-works page is the full instructions until one is written.

£29.00 a month · 500 runs · one workflow · HubSpot and Resend