# Workflow examples you can copy

> Ten complete workflows for a field service app: welcome emails, overdue invoice reminders, PDF invoices, weekly exports, webhook leads, AI triage and more.

Source: https://tadabase.com/docs/workflows/workflow-recipes-and-examples  
Status: Verified Nov 17, 2026. Checked against the current product

Each example below is a complete workflow for a field service app with **Customers**, **Jobs**, **Technicians** and **Invoices** tables. Copy the trigger and steps, then swap in your own tables and fields. Field names such as Status or Due Date are examples; use the fields your tables have.

> **Note:** Values from an earlier step are picked in a later step's value picker under **Step Data**. Values from the workflow's own record are under the trigger's record. See [Use values from the trigger and earlier steps](https://tadabase.com/docs/workflows/using-workflow-data).

## 1. Welcome a new customer

**What it does:** emails every new customer a welcome message.

| Part | Setting |
| --- | --- |
| Trigger | **Record Created** on **Customers** |
| Step 1 | **Send Email**: a welcome email template, sent to the customer's email field. |

See [Send an email from a workflow](https://tadabase.com/docs/workflows/communication-actions).

## 2. Remind customers about overdue invoices every morning

**What it does:** every day at 8:00, emails the customer of each unpaid invoice that is past its due date, and stamps the invoice.

| Part | Setting |
| --- | --- |
| Trigger | **Schedule** on **Invoices**: Run **Daily** at 8:00. Under **Record Selection**, add filters for invoices that are not paid and whose due date has passed. |
| Step 1 | **Send Email** to the email of the invoice's customer (a connected value), with the invoice number and amount in the template. |
| Step 2 | **Update Record** on the invoice: set a Last Reminder field to **Current Date & Time**. |

A scheduled workflow runs its steps once for each record that matches **Record Selection**. See [Run a workflow on a schedule](https://tadabase.com/docs/workflows/scheduled-workflows).

## 3. Assign a free technician to a new job

**What it does:** when a job is created, finds an available technician, connects them to the job and tells them.

| Part | Setting |
| --- | --- |
| Trigger | **Record Created** on **Jobs** |
| Step 1 | **Find Records** on **Technicians**: filter Status is Available, sort by the number of open jobs from low to high, **Record Limit** 1. Name the step "Find free technician". |
| Step 2 | **Update Record** on the job: set the Technician connection to the record from "Find free technician" under **Step Data**. |
| Step 3 | **Send Email** to the technician's email from the same step. |

If no technician is free, Find Records is skipped and the next steps have no technician to use. Add a condition on its **Records Found** to handle that case. See [Find records and use them in later steps](https://tadabase.com/docs/workflows/find-records-in-a-workflow).

## 4. Send a PDF invoice when a job is completed

**What it does:** when a job's status changes to Completed, makes a PDF invoice from a PDF Page, saves it on the job and emails it to the customer.

| Part | Setting |
| --- | --- |
| Trigger | **Record Updated** on **Jobs** |
| Step 1 | **Add Condition**: Status is Completed, and the job's Invoice PDF file field is blank. Add the next steps under **Yes**. |
| Step 2 | **Create PDF Page**: the job as the record source, your invoice PDF Page, saved to the job's Invoice PDF field. |
| Step 3 | **Send Email** to the customer, with the Create PDF Page step chosen under **Attachments**. |

The blank-file rule stops a second invoice when someone edits the job again later. PDF steps depend on your plan. See [Create a PDF from a workflow](https://tadabase.com/docs/workflows/document-actions).

## 5. Email a weekly CSV of completed jobs

**What it does:** every Monday morning, exports the completed jobs to a CSV file and emails it to the office manager.

| Part | Setting |
| --- | --- |
| Trigger | **Schedule** on **Users**: Run **Weekly** at 7:00. Under **Record Selection**, filter to the office manager's user and set **Limit** to 1, so the workflow runs once. |
| Step 1 | **Export to CSV**: **Export from table** Jobs, with a filter for completed jobs and the columns you want. |
| Step 2 | **Send Email** to the user's email, with the Export to CSV step chosen under **Attachments**. |

A scheduled workflow runs once per selected record. Picking one user with **Limit** 1 is how you get exactly one email per week.

## 6. Add a customer from another service's webhook

**What it does:** when a website form or another service posts a new lead, adds it as a customer.

| Part | Setting |
| --- | --- |
| Trigger | **Incoming Webhook**. Save the workflow, send one test request and capture it as the sample. |
| Step 1 | **Transform JSON** (optional): rename or remove fields in the payload so they match your table, for example `contact.full_name` to `name`. |
| Step 2 | **Create Record** in **Customers**: map each field to a value from the Transform JSON step under **Step Data**, or straight from the webhook's data. |

The Incoming Webhook trigger is on the Business Growth, Pro and Elite plans. See [Receive data from another service with an incoming webhook](https://tadabase.com/docs/integrations/incoming-webhooks).

## 7. Stamp a user's last login

**What it does:** records when each user last logged in.

| Part | Setting |
| --- | --- |
| Trigger | **User Event**, event **User Logged In** |
| Step 1 | **Update Record** on the user's record: set a Last Login field to **Current Date & Time**. |

## 8. A "Mark as completed" button on each job

**What it does:** a technician clicks a button on a job to close it, and sees a confirmation.

| Part | Setting |
| --- | --- |
| Trigger | **Manual** on **Jobs** |
| Step 1 | **Update Record** on the job: Status to Completed, a Completed At field to **Current Date & Time**. |
| Step 2 | **Show Message**: a short toast such as "Job closed". |
| Page | Add a button that starts this workflow to the jobs table or job details page. See [Start a workflow from a page or a button](https://tadabase.com/docs/workflows/triggering-workflows-from-pages-and-buttons). |

Because the job's status changes, example 4 runs next and sends the invoice.

## 9. Calculate an invoice total with code

**What it does:** works out an invoice's subtotal and total with tax whenever the invoice is saved.

| Part | Setting |
| --- | --- |
| Trigger | **Record Created or Updated** on **Invoices** |
| Step 1 | **Run Custom Code** with two inputs from the invoice: `hours` and `rate` (**Record Value (Source)**). Code below. |
| Step 2 | **Update Record** on the invoice: set Subtotal and Total from the Run Custom Code step under **Step Data**. |

```javascript
const hours = Number($hours || 0);
const rate = Number($rate || 0);
const subtotal = hours * rate;

returnData("subtotal", subtotal);
returnData("total", Math.round(subtotal * 1.0875 * 100) / 100);
```

The update in step 2 does not start this workflow again: a workflow's own changes never re-trigger it. See [Run custom JavaScript in a workflow](https://tadabase.com/docs/workflows/running-custom-javascript).

## 10. Let AI set a job's priority

**What it does:** reads a new job's description, sets its priority and alerts the dispatcher about urgent jobs.

| Part | Setting |
| --- | --- |
| Trigger | **Record Created** on **Jobs** |
| Step 1 | **AI Prompt**: a prompt that receives the job's description and answers with one word: Low, Normal or Urgent. |
| Step 2 | **Update Record** on the job: set Priority to the AI Prompt step's answer under **Step Data**. |
| Step 3 | **Add Condition**: the AI Prompt answer is Urgent. Under **Yes**, **Send Email** to the dispatcher. |

AI Prompt steps depend on your plan and use your daily AI allowance. See [Use an AI prompt in a workflow](https://tadabase.com/docs/ai-features/use-an-ai-prompt-in-a-workflow).

## Before you turn a copied workflow on

- Name each step after what it does, such as "Find free technician". The name is what you pick under **Step Data** later.
- For a scheduled workflow, check its **Record Selection** filters, then use **Dry run** to see what it would do without changing anything.
- Type a **Version note** before you save, so you can find this version again. See [Restore a workflow version and organize workflows](https://tadabase.com/docs/workflows/workflow-versions-and-folders).
- Check the first real runs in **History**. See [Check workflow runs, history and errors](https://tadabase.com/docs/workflows/workflow-history-and-logs).
- Tag related workflows, for example "Invoices", to find them quickly in the list.
