Module · The Builder✅Knowledge checkCheck: can you build and read one?5 questions · Pass at 60%1. A workflow is trigger → lookup → email. The email node references the trigger and the value will not resolve, even though the execution log clearly shows it. Why?The trigger's data expires once a later node has runTrigger values must be copied into a variable before useA node sees only what is wired directly into itTrigger references use a different syntax from node references2. You open a run and a task's title reads <crmmanager_1.frist_name not found>. What kind of problem is that?A typo — the reference named a field that does not existMissing data — the contact genuinely has no first nameA permissions problem — the node could not read that fieldA timing problem — the value had not been produced yet3. You are configuring a node that can do several jobs. Which decision do you make first?The integration, since nothing runs until an account is chosenThe variables, since they take the longest to get rightThe operation, since the panel reshapes itself around itOrder does not matter; the fields are independent of each other4. A run shows completed, with no failed nodes. What has it actually told you?That the workflow did what you intended, since nothing erroredThat every node produced a non-empty output of some kindThat the data was valid, since bad data would have failed a nodeVery little — a completed run may well have mailed nobody5. You built a workflow, saved it, created a contact, and nothing happened at all — no run, no error, nothing in the history. What do you check first?Whether the workflow was ever activatedWhether the field names in the action node are rightWhether the contact had all of its fields filled inWhether the two nodes are actually connectedCheck answers← Back to Get Started with the Workflow Builder
