comms

Your code names a template and a language. Which provider carries it, and what the message actually says, are configuration — so changing either is not a deploy.

email.send

email.send(params) → null

const { data, error } = await nulvless.comms.email.send({
  to: '[email protected]',
  template: 'grants-invite',
  language: 'pt-BR',
  params: { organization: 'Acme Inc', role: 'admin' },
});

sms.send

sms.send(params) → null

The same shape, with phone instead of to.

await nulvless.comms.sms.send({
  phone: { country_code: '+55', number: '11987654321' },
  template: 'phone-otp-verification',
  language: 'en-US',
  params: { code: '492013' },
});

Sends are quota-limited per channel. Exhausting it answers 429 rate_limit_exceeded — with no retryAfter, unlike the auth service, so keep your own backoff.

email.test and sms.test

test(recipient) → null

Sends a probe so you can confirm the provider is wired before a real message depends on it.

await nulvless.comms.email.test('[email protected]');

Worth running from your deploy pipeline against a fresh environment — a misconfigured provider is otherwise invisible until the first user needs a verification code.

Built-in templates

Every environment starts with the templates the platform itself needs. These are the slugs, and each is editable:

A template is per channel: the email and SMS versions of the same idea are separate slugs, because wording that works in an inbox does not survive 160 characters.

templates

list · get · create · update · delete

await nulvless.comms.templates.list({ channel: 'email' });
await nulvless.comms.templates.get('email', 'welcome-user', 'pt-BR');
await nulvless.comms.templates.create(params);
await nulvless.comms.templates.update('email', 'welcome-user', params, 'pt-BR');
await nulvless.comms.templates.delete('email', 'welcome-user', 'pt-BR');

Everything but create and list is addressed by channel + slug + language. That triple is the identity of a template — there is no id to hold onto, and the same slug in two languages is two records.

Most teams edit these in the console. The API exists for when you version them alongside your application.

create

update takes the same optional fields minus slug, channel and language — those identify the template rather than describe it.

The webhook channel

Besides email and SMS a template can be a webhook: instead of rendering a message for a person, it posts to a url you own. The call site is identical — same slug, same params — so a notification can move from email to a webhook as configuration, without touching the code that triggers it.

The Template object

Why name a template

Naming a template instead of composing a message is what makes the rest work:

• Per language — the same call renders pt-BR or en-US from one slug.
• Per environment — development points at a sandbox provider, so a test never reaches a real inbox.
• Per channel — email and SMS versions of one message are edited side by side.

None of that requires the calling code to change.

Next