Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

QR Code Coupon Workflow for Leads

QR Code Coupon Workflow for Leads is a 21-node automation blueprint connecting Google Sheets, SuiteCRM, SMTP Email. Inspect its trigger, execution graph, branches, and implementation requirements.

Google SheetsSuiteCRMSMTP Email

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

21

Nodes

19

Links

2

Run groups

Connected tools

3 integrations

  • Google Sheets
  • SuiteCRM
  • SMTP Email

Canvas controls

Fit wide systems, then zoom into any run group.

QR Code Coupon Workflow for Leads execution lanes2 run groups containing 21 workflow nodes and 19 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.On form submission. trigger node, formTrigger. 0 incoming and 1 outgoing connections.STARTOn form submissionTRIGGERFORMTRIGGER0 IN / 1 OUTForm Fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Form FieldsTRANSFORMSET1 IN / 1 OUTDuplicate Lead?. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 03Duplicate Lead?GOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTIs Duplicate?. decision node, if. 1 incoming and 1 outgoing connections.STEP 04Is Duplicate?DECISIONIF1 IN / 1 OUTGet Coupon. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 05Get CouponGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTToken SuiteCRM. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 06Token SuiteCRMINTEGRATIONHTTPREQUEST1 IN / 1 OUTCreate Lead SuiteCRM. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 07Create Lead SuiteCRMINTEGRATIONHTTPREQUEST1 IN / 1 OUTUpdate Sheet. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 08Update SheetGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTGet QR. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 09Get QRINTEGRATIONHTTPREQUEST1 IN / 1 OUTSend Email. integration node, emailSend. 1 incoming and 0 outgoing connections.OUTCOMESend EmailINTEGRATIONEMAILSEND1 IN / 0 OUTWebhook. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhookTRIGGERWEBHOOK0 IN / 1 OUTSet coupon. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Set couponTRANSFORMSET1 IN / 1 OUTIf. decision node, if. 1 incoming and 2 outgoing connections.STEP 03IfDECISIONIF1 IN / 2 OUTGet Lead. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 04Get LeadGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTNo coupon. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.STEP 04No couponTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTNot used?. decision node, if. 1 incoming and 2 outgoing connections.STEP 05Not used?DECISIONIF1 IN / 2 OUTToken SuiteCRM 1. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 06Token SuiteCRM 1INTEGRATIONHTTPREQUEST1 IN / 1 OUTCoupon KO. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.STEP 06Coupon KOTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTUpdate Lead. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 07Update LeadINTEGRATIONHTTPREQUEST1 IN / 1 OUTUpdate coupon used. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 08Update coupon usedGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTCoupon OK. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.OUTCOMECoupon OKTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.21 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

On form submission

9 Execution Links

  1. Start

    On form submission

    Trigger

  2. Step 2

    Form Fields

    Transform

  3. Step 3

    Duplicate Lead?

    Integration

  4. Step 4

    Is Duplicate?

    Decision

  5. Step 5

    Get Coupon

    Integration

  6. Step 6

    Token SuiteCRM

    Integration

  7. Step 7

    Create Lead SuiteCRM

    Integration

  8. Step 8

    Update Sheet

    Integration

  9. Step 9

    Get QR

    Integration

  10. Outcome

    Send Email

    Integration

02

Run Group

Coupon OK

10 Execution Links

  1. Start

    Webhook

    Trigger

  2. Step 2

    Set coupon

    Transform

  3. Step 3

    If

    Decision

  4. Step 4

    Get Lead

    Integration

    No coupon

    Trigger

  5. Step 5

    Not used?

    Decision

  6. Step 6

    Token SuiteCRM 1

    Integration

    Coupon KO

    Trigger

  7. Step 7

    Update Lead

    Integration

  8. Step 8

    Update coupon used

    Integration

  9. Outcome

    Coupon OK

    Trigger

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas