@protobase/cli 0.71.2 → 0.71.3

package/dist/cli/package.js

@@ -1,4 +1,4 @@
 //#region package.json
-var version = "0.71.2";
+var version = "0.71.3";
 //#endregion
 export { version };

package/dist/config/build-project.js

@@ -1,6 +1,6 @@
 import { projectFiles, projectFunctions, projectJobs, projectNotifications, projectOptions, projectResources, projectWebhooks, projectWorkflows } from "./project-parts.js";
 import { userTablesOn } from "./user-tables-config.js";
-import { buildAppAuth, buildAuthenticator, checkCallsOptions, checkStatusOptions } from "@protobase/server/internal";
+import { buildAppAuth, buildAuthenticator, checkCallsOptions, checkStatusOptions, workflowPlugins } from "@protobase/server/internal";
 //#region src/config/build-project.ts
 /**
 * The app's own mailer, the default export of its auth/mailer.ts: what sign-in and the jobs (`context.mail`) both send
@@ -34,9 +34,9 @@ const projectAuth = async (config, { db, pool }, workflows) => {
 		...workflows && { workflowConnections: workflowConnectionsOf(workflows) }
 	});
 };
-/** The connections the workflows' plugins declare, which people connect accounts through at sign-in. */
+/** The connections the workflows' plugins declare, the defaults' among them, which people connect accounts through at sign-in. */
 const workflowConnectionsOf = (workflows) => ({
-	declared: (workflows.plugins ?? []).flatMap(({ plugin }) => Object.entries(plugin.connections ?? {}).map(([name, declaration]) => ({
+	declared: workflowPlugins(workflows.plugins).flatMap(({ plugin }) => Object.entries(plugin.connections ?? {}).map(([name, declaration]) => ({
 		plugin: plugin.name,
 		name,
 		declaration

package/dist/config/project-parts.js

@@ -192,7 +192,7 @@ const projectWebhooks = async (config) => {
 		...ownerRoles && { ownerRoles }
 	};
 };
-const workflowPlugins = async (config, packages) => {
+const workflowPlugins$1 = async (config, packages) => {
 	const project = config.sources.at(-1).files;
 	const fromPackages = await Promise.all(packages.map(async (name) => ({
 		plugin: (await project.package(name)).default,
@@ -209,7 +209,7 @@ const projectWorkflows = async (config) => {
 	if (!config.workflows) return void 0;
 	const { plugins: packages = [], ...options } = config.workflows;
 	const savedByRoles = await lastDefault(config, "workflows/saved-by-roles.ts");
-	const plugins = await workflowPlugins(config, packages);
+	const plugins = await workflowPlugins$1(config, packages);
 	return {
 		...options,
 		...savedByRoles && { savedByRoles },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@protobase/cli",
-  "version": "0.71.2",
+  "version": "0.71.3",
   "description": "The protobase command: scaffold, doctor, dev, build and serve a Protobase project.",
   "license": "Apache-2.0",
   "repository": {
@@ -43,13 +43,13 @@
   "dependencies": {
     "@better-auth/core": "^1.7.12",
     "@hono/node-server": "^2.1.3",
-    "@protobase/config": "0.71.2",
-    "@protobase/layout": "0.71.2",
-    "@protobase/query": "0.71.2",
-    "@protobase/schema": "0.71.2",
-    "@protobase/server": "0.71.2",
-    "@protobase/ui": "0.71.2",
-    "@protobase/workflows": "0.71.2",
+    "@protobase/config": "0.71.3",
+    "@protobase/layout": "0.71.3",
+    "@protobase/query": "0.71.3",
+    "@protobase/schema": "0.71.3",
+    "@protobase/server": "0.71.3",
+    "@protobase/ui": "0.71.3",
+    "@protobase/workflows": "0.71.3",
     "@react-email/render": "^2.1.0",
     "@scalar/hono-api-reference": "^0.12.10",
     "@sentry/vite-plugin": "^11.10.0",

package/skills/protobase/references/features/workflows.md

@@ -25,4 +25,5 @@ Graphs of steps the server runs along their edges, written in a language a model
 - [Guarded requests for plugins](../reference/workflow-plugins.md#sending-requests) (beta): A plugin's requests reach only public addresses, follow no redirect and read at most 10 MiB.
 - [Webhook trigger](../reference/workflows.md#appwebhook) (beta): A workflow starts from a signed call to a URL of its own, limited in size and rate.
 - [Polling triggers](../reference/workflow-plugins.md#polling-and-webhook) (beta): A workflow starts once for each new item a plugin finds on a schedule, or at each time of a cron with `app:schedule`.
+- [Incoming Gmail mail](../reference/workflow-plugins.md#incoming-gmail-mail) (beta): A workflow starts once for each new mail on a label of a connected Gmail mailbox that passes optional sender, recipient and subject filters, read with read-only access within about a minute; not yet checked against a real Google account.
 - [Connected accounts](../reference/workflows.md#connecting-an-account) (beta): People connect their own accounts at other services through OAuth from the account page, see which workflows use each one, and MCP clients list them to bind. A workflow's steps and triggers sign in with one only once its owner turned the workflow on, with tokens encrypted and refreshed. Disconnecting deletes the token and revokes it at a provider that has a revocation endpoint, trying again for a few hours when the provider does not take it, and says which it did.

package/skills/protobase/references/reference/workflow-plugins.md

@@ -8,7 +8,7 @@ Add trigger and step types to workflows from a file of the app or a package, thr
 Plugins add step types and record triggers. They also add polling and webhook triggers, which run within the limits named in their section, and connections that sign in to other services as an account a person connected, within the limits named under [Connections](#connections).
 :::
 
-A **workflow plugin** adds trigger and step types to an app's [workflows](workflows.md). Its types are named `<plugin>:<key>`, such as `acme:create_invoice`: a Task names a step type as its `Resource`, and a definition's `trigger` holds a trigger type with its input. The built-in types, `app:http`, `app:records.*`, `app:mail.send` and `app:record`, are a plugin like any other, written on this interface alone, so a plugin's types run, are checked and are listed exactly as they are.
+A **workflow plugin** adds trigger and step types to an app's [workflows](workflows.md). Its types are named `<plugin>:<key>`, such as `acme:create_invoice`: a Task names a step type as its `Resource`, and a definition's `trigger` holds a trigger type with its input. The built-in types, `app:http`, `app:records.*`, `app:mail.send` and `app:record`, are a plugin like any other, written on this interface alone, so a plugin's types run, are checked and are listed exactly as they are. So is every [default plugin](#default-plugins), such as [incoming Gmail mail](#incoming-gmail-mail).
 
 ## Writing a plugin
 
@@ -46,6 +46,8 @@ export default definePlugin({
 })
 ```
 
+For a whole plugin to read, with a connection, a polling cursor, a refused token and bounded run input, see the Gmail plugin's source, `packages/workflow-plugins/src/gmail/` in the repository, which [the next section](#incoming-gmail-mail) describes.
+
 `definePlugin` checks the plugin's names: its `name` is lowercase letters, digits and `_`, each type's key is lowercase words joined by `_` or `.`, and a type that names a connection must find it among the plugin's `connections`.
 
 ### Installing it
@@ -53,7 +55,7 @@ export default definePlugin({
 - **The app's own:** the default export of `workflows/plugins/<name>.ts`, found by its path as jobs are. An [extension](config.md#extensions) adds its own from its folder.
 - **From a package:** listed by name in [`workflows.plugins`](config/jobs-and-events.md#workflowsplugins), its default export the plugin. The package is a dependency of the app.
 
-Two plugins of one name stop startup, naming both. A plugin is server code that runs with the app's rights, like the app's own code: load only plugins you trust. The interface's version is `pluginApi`, `1`; releases add optional keys to it and never break it.
+Two plugins of one name stop startup, naming both. The exception is an app's own plugin named like a [default plugin](#default-plugins) other than `app`, which takes that default's place, such as one that pins its own version. A plugin is server code that runs with the app's rights, like the app's own code: load only plugins you trust. The interface's version is `pluginApi`, `1`; releases add optional keys to it and never break it.
 
 ## Step types
 
@@ -231,6 +233,57 @@ The token is blanked out of the step's logs, error and output, and out of the tr
 
 An account connected through a provider of a connection's own never signs anyone in to the app, and never signs anyone up. <gap>A connection cannot be shared between people of an organization because shared connections are not implemented; each account is its owner's alone.</gap>
 
+## Default plugins
+
+Every app has these plugins besides `app`. A type that signs in is offered once the app can make its connection, as [Connections](#connections) says.
+
+### Incoming Gmail mail
+
+:::caution[Beta]
+The Gmail plugin is tested against a stand-in of Gmail's API written to Google's published reference, but has not yet been checked against a real Google account. Mail starts its run within about a minute of arriving, not at once.
+:::
+
+`gmail:new_mail` starts one run for each new mail on a label of a connected Gmail mailbox. It reads the mailbox with read-only access, so a workflow it starts cannot send, change or delete mail through it.
+
+To use it, turn on Google sign-in (`auth.socialProviders.google`) with `auth.encryptOAuthTokens`, and add the scope `https://www.googleapis.com/auth/gmail.readonly` to the app's Google consent screen (Data Access), as [Send mail from Gmail](../guides/send-from-gmail.md) does for its own scope. `gmail.readonly` is a restricted scope: until Google has verified the app, the consent screen warns that the app is unverified, and at most 100 people can connect. The person whose mailbox it is connects their Google account under **Connections** on the account page, binds that account in the workflow and turns the workflow on:
+
+```json
+{ "trigger": { "gmail:new_mail": { "label": "INBOX", "from": "@supplier.example", "subject": "invoice" } }, "connections": { "gmail:google": "<account id>" }, "stateMachine": { ... } }
+```
+
+| Input | What it does |
+| --- | --- |
+| `label` | The label to watch, by name or id. Default `INBOX`. A label the mailbox does not have fails the trigger, naming it. |
+| `from` | Only mail whose sender's name or address contains this. |
+| `to` | Only mail with a To or Cc recipient whose name or address contains this. |
+| `subject` | Only mail whose subject contains this. |
+
+Each filter ignores case, and a mail must pass every filter that is set. A mail without the value a filter reads, such as one with no sender, does not pass.
+
+A run's input is the mail:
+
+```json
+{
+  "message_id": "18c2f0a9d3e4b5a6",
+  "thread_id": "18c2f0a9d3e4b5a6",
+  "from": { "name": "Ada", "address": "ada@example.com" },
+  "to": [{ "name": "Grace", "address": "grace@example.com" }],
+  "cc": [],
+  "subject": "Invoice 7",
+  "date": "2026-11-05T10:00:00.000Z",
+  "text": "Attached.",
+  "html": "<p>Attached.</p>",
+  "attachments": [{ "filename": "invoice-7.pdf", "content_type": "application/pdf", "size": 48213 }],
+  "truncated": false
+}
+```
+
+- **The values** are as the mail states them, and `null` where it states none. `html` is the sender's own markup: treat it as untrusted wherever a workflow passes it on. Attachments come as their names, types and sizes, not their content.
+- **Bounds:** each value has a fixed most length, such as 1,000 characters for the subject and 128 Ki characters for `text` and for `html`, and at most 50 recipients of each kind and 50 attachments. When the mail is still too large, `html` and then `text` are left out. A mail over about 7.5 MiB, whose answer from Gmail, in base64, is then over 10 MiB, or one too deeply nested to read, gives its headers alone, with `text`, `html` and `attachments` as `null`. A NUL character, or half of a character's surrogate pair, is left out, since the database cannot store it. `truncated` is `true` whenever something was cut short or left out.
+- **When it starts:** from the moment the workflow is turned on. Mail already in the mailbox starts no run.
+- **Polling:** every minute, the trigger reads the mailbox's history after where it stood, at most 90 mails a poll and the rest on the next poll, so each mail starts one run and none is skipped. Every mail it reads counts toward the 90, whether or not it passes the filters. Two triggers on one mailbox share Google's quota for that mailbox. When Google no longer keeps the history after the trigger's place, which can happen after a long time off, the trigger lists the label's mail since its last full read instead, 90 a poll, and then goes on from the history. <gap>A new Gmail mail cannot start its run at once because push notices from the mailbox are not implemented; the trigger polls every minute.</gap>
+- **Sign-in:** the token is refreshed when it expires. When Google refuses the refresh, or refuses the token twice in a row, the trigger waits for the account's owner to connect it again, as [Polling and webhook](#polling-and-webhook) describes.
+
 ## The type list
 
 [`list_workflow_types`](mcp.md#workflows) over MCP lists every step and trigger type the app has, built-in and plugin ones alike, as their plugins declare them: id, label, description, input and output schemas, errors, connection and a step type's cache advice (`choice`, `default` and `disclaimer`), with `available: false` and a reason for a type the app cannot run. A save, and `validate_workflow`, check a definition against the same list.