All articles Fraud & ATO

Risky Signups CRM Workflow: Route Them Automatically

Glowing blue decision gate branching into three translucent panels on a black background

A risky signups CRM workflow connects your risk decision to the tool your sales team actually works in. Without it, a fake free trial lands in HubSpot as a normal new lead, a rep spends the morning on a disposable address, and the pipeline stops matching reality. The decision itself — allow, step up, block — is the simple part. The work is delivering that decision to HubSpot, Salesforce or Pipedrive with enough context that nobody has to guess what happened.

Prynt Automate handles that last mile: workflows triggered by decisions and events, with steps that write a CRM record, post to Slack, call a signed webhook or add a Google Sheets row, plus retries and a run log. This guide builds one workflow you can ship this week — Control decides, Automate routes, sales works a clean list.

Which signups deserve their own path

Route by meaning, not by volume. Three groups need different handling: scripted traffic that fills forms, identities you cannot trust — VPN, proxy, Tor, datacenter networks, tampered or recycled device fingerprints — and people abusing a policy, such as the same device claiming a trial or bonus twice.

Prynt Control answers a fixed set of use cases (signup, free_trial, bonus, login, checkout, extra_seat, sms, paywall) with allow, step-up or block, a reason code and a suggested step such as captcha, verify_email or card_or_passkey. The middle answer is the one most teams underuse: a risky signup usually should be verified, not refused. That distinction is also what makes CRM routing worth building, because a blocked signup has no lead to hand over, while a stepped-up signup has a lead that is simply not ready yet.

If your noise is mostly scripted, start with our bot detection guide. If it is one device coming back with new emails, the signal you want is device fingerprinting.

Turn the decision into three routing rules

One workflow with three branches is easier to maintain than three workflows with overlapping filters.

Three translucent glass columns receiving blue light streams, representing three routing paths

  • allow — create or update the CRM record, assign the owner, and notify in Slack only when the account fits your target profile.
  • step-up — write the record but park it: lifecycle stage “pending verification,” no owner, no task, promoted only when the suggested step completes.
  • block — create no person record at all. Send the event to Slack and to a Google Sheets row instead; every blocked signup you push into the CRM teaches your reps to ignore the CRM.

Keep the CRM step idempotent: pass requestId as the deduplication key so a retried run updates the same record instead of creating a second one.

Build the workflow in Prynt Automate

Start from the decision event, then keep the steps short: filter on the decision, write the CRM record, post to Slack, append the Sheets row. Automate exposes a small set of template variables, so you never parse the payload by hand:

{
  "decision": "{{trigger.decision}}",
  "riskScore": "{{trigger.riskScore}}",
  "visitorId": "{{trigger.visitorId}}",
  "requestId": "{{trigger.requestId}}",
  "url": "{{trigger.url}}",
  "reasons": "{{trigger.reasons | json}}"
}

Use {{steps.s1.output.text}} to pass the output of an earlier step — a lookup, a webhook response — into the next one. Put a decision filter before the CRM step as well, so a duplicate run stops there instead of updating a record twice.

Automate is priced at $39 per 1,000 executions, so route decisions, not page views. One execution per decision is a predictable cost; wiring page views into the same workflow multiplies it for no extra signal.

What sales needs on the record

Write fields a rep can act on, not a raw JSON blob: decision, riskScore, reason codes, visitorId, requestId, suggested step and timestamp. Keep reason codes in a text field rather than a picklist you will outgrow.

Developer working at night in a dark office lit by cool blue light

Never let the workflow set a stage that means “qualified.” A risky-but-allowed account belongs in its own lifecycle stage, so pipeline reports stay honest. Put the suggested step in the task text: a rep who reads “request a card or passkey” knows what to do next, while “fraud: high” only creates work for you.

Keep a Google Sheets row you can defend

Your CRM is a sales tool, not an audit log. Append every decision — including the blocked ones the CRM never sees — to one Sheets tab with a fixed column order: timestamp, use case, decision, riskScore, reasons, suggested step, visitorId, requestId, CRM record id, workflow run id.

That sheet is where risk and sales ops meet. It shows whether your thresholds fire on the traffic you expected, and it answers “why was this account blocked?” with data instead of a screenshot.

Run it in mirror mode first

Control has a 14-day mirror period: it returns decisions and reasons and blocks nothing while your code is not acting on them — which is exactly when you should build the CRM mapping. Watch the sheet for a week, confirm the reason codes you see are the ones your filters expect, then turn on the step-up branch before the block branch. Keep the run log and send failed runs to the Slack channel your reps already read. The platform overview shows how the products share one browser agent, one account and one bill.

Grid of translucent tiles with one blue-highlighted row linked to a rounded card

FAQ

Does Prynt block risky signups for me?

No. Control returns allow, step-up or block with a reason code, and your code decides what to do with it. Automate moves that decision into the systems your team already uses.

What happens when a workflow run fails mid-way?

Automate retries steps and records every run in the run log. With requestId as the dedupe key, a retry updates the existing CRM record instead of creating a duplicate lead.

Can I route to Google Sheets without a CRM?

Yes. Sheets is a step of its own, so a Sheets-only workflow works while you evaluate, or as a permanent audit trail alongside HubSpot, Salesforce or Pipedrive.

Start at pryntid.com with a free account, let Control answer decisions through its mirror period, and point Automate at the CRM you already run. When the sheet looks right, switch the branches on.

Try it free

Prynt is device intelligence with a free plan: 5,000 identifications a month, visitor IDs with confidence and bot detection — no credit card. Upgrade to Pro for VPN, proxy, tampering and behavioral signals.

Keep reading