Log in with SMS OTP codes

Single-number setup

If you only need OTP login from one fixed number (or your tests don’t run in parallel), fetch the latest message and pull the code out:

const msg = await sms.fetchLatest({
  to: "+18888888888",
  afterDate: new Date(Date.now() - 60_000),
  timeout: 30_000,
});

const [code] = msg.body.match(/\b\d{6}\b/) ?? [];
if (!code) throw new Error("No OTP code found in SMS");
setVariable("OTP_CODE", code);

Then add a Type step with value {{ env.OTP_CODE }}.

Parallel runs against the same OTP flow

If you run the same OTP login test in parallel (e.g. multiple shards in CI), two tests can race on the same inbound code. Lease a number from your pool so each shard gets its own. Momentic releases it back to the pool when the test finishes.

const { phoneNumber } = await sms.lease();

// trigger your app's "Send code" flow against `phoneNumber`

const msg = await sms.fetchLatest({
  to: phoneNumber,
  afterDate: new Date(Date.now() - 60_000),
  timeout: 30_000,
});

const [code] = msg.body.match(/\b\d{6}\b/) ?? [];
if (!code) throw new Error("No OTP code found in SMS");
setVariable("OTP_CODE", code);

See sms.lease() for full options (TTL, fail-fast, optional manual release).

Both examples poll for up to 30 seconds, well within the JavaScript step’s 90-second default timeout. For longer polls, raise the step’s Timeout field, up to 600 seconds.

Overview

Migrate to Momentic

Frameworks

Use cases

Triage

AI actions

Authentication

Page interactions

Test data & variants

Visual testing

Reporting

Upgrading

Log in with SMS OTP codes

Single-number setup

Parallel runs against the same OTP flow

​Single-number setup

​Parallel runs against the same OTP flow

​Related

Single-number setup

Parallel runs against the same OTP flow

Related