Welcome email

What it adds to your app

One workflow: on signup, email the new person.

How its workflows run

Each one is a server workflow in your project: it runs on its trigger, with retries, and its runs show in the builder's log.

1. Welcome new ‹person› by email

   When a row changes: ‹person› created. Then: Send email.

Set it up

It merges into the contract of an app you already have. Nothing is overwritten: a name you already use is refused until you pass a prefix.

1. Pick the project

   Use the button above, or ask your coding agent with the Appbricx MCP server connected (quickstart).

2. Point it at your tables and roles

   Leave out the ones with defaults; a wrong one is refused with the options your app has.

   Param	What it is	Example
   person	The table a new person lands in when they sign up (usually named after the role, like customer or member). Optional.	customer
   email_field	The email field on that table the welcome goes to. Optional.	email

3. Preview, then apply to dev

   A dry run shows the diff and the check report; applying it changes your dev environment only.

4. Deploy

   When dev looks right, deploy. Production gets a snapshot first, so you can roll back.

Use it with your coding agent

The agent reads the template, runs a dry run, shows you the diff and applies it.

Add the Welcome email template (slug "welcome-email") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (person: who signs up; email_field: their email field).

{
  "tool": "use_template",
  "arguments": {
    "slug": "welcome-email",
    "project_id": "<your project id>",
    "params": {
      "person": "customer",
      "email_field": "email"
    },
    "dry_run": true
  }
}

appbricx templates use welcome-email --param person=customer --param email_field=email --dry-run