Skip to main content
The TFA (Two-Factor Authentication) node handles 2FA challenges during workflow execution. It automatically extracts verification codes from SMS or email, generates TOTP codes from authenticator secrets, extracts and follows magic links from emails, or answers security questions from the vault. This requires proper account configuration (email forwarding, SMS webhook setup, TOTP secret storage, or stored security questions). See the Two-Factor Authentication guide for setup instructions.

Parameters

TFA Types

SMS

Automatically extracts the verification code from an SMS message. Requires usage of the CloudCruise phone number shown in your vault entry.

EMAIL

Automatically extracts the verification code from an email. Requires email forwarding to be configured or direct usage of the CloudCruise email shown in your vault entry.

AUTHENTICATOR

Generates a TOTP code using the stored authenticator secret. No external service needed. To use a different seed, store it as a Totp additional field on the credential and set tfa_field to the field’s name. The step fails with a clear error if the field is missing, is not of type Totp, or was skipped from a secret provider item. Automatically extracts the magic login link from an email and navigates to it. Requires email forwarding to be configured or direct usage of the CloudCruise email shown in your vault entry.

SECURITY_QUESTION

Answers a security question with an answer stored on the credential’s security questions.
  • STATIC: reads the text of question_selector, finds the matching stored question and types its answer into selector.
  • LLM_VISION: a vision model reads the question text from a screenshot and locates the answer field. selector and question_selector are not needed.
Matching. The page question is first compared with the stored questions after normalization, without a model call. If none matches exactly and fuzzy_match is true, a model picks the stored question that asks for the same information, accepted only with high confidence. Only question texts reach a model, never answers. The answer is typed like a password and masked in run logs. It is never available as a workflow variable. Errors. The step fails with AUTHENTICATION-E0001 when:
  • no stored question matches: No stored security question of credential BANK matches the page question "Name of your first school?"
  • the credential has no questions: Credential BANK has no security questions

Notes

  • The credential parameter references a vault credential key, such as the permissioned_user_id used for the phone number, email address, TOTP secret, or security questions
  • Codes are automatically entered and submitted (pressing Enter) after extraction. No subsequent Click action on a “Verify” or “Submit” button is required
  • For more details on 2FA setup, see the Two-Factor Authentication guide