@project-ajax/create 0.0.28 → 0.0.31

package/dist/index.js

@@ -94,14 +94,12 @@ function printNextSteps(directoryName) {
   if (directoryName === ".") {
     console.log(`
   ${chalk.bold("npm install")}
-  ${chalk.bold("npx workers auth login")}
   ${chalk.bold("npx workers deploy")}
     `);
   } else {
     console.log(`
   ${chalk.bold(`cd ${directoryName}`)}
   ${chalk.bold("npm install")}
-  ${chalk.bold("npx workers auth login")}
   ${chalk.bold("npx workers deploy")}
     `);
   }

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@project-ajax/create",
-	"version": "0.0.28",
+	"version": "0.0.31",
 	"description": "Initialize a new Notion Project Ajax extensions repo.",
 	"bin": {
 		"create-ajax": "dist/index.js"

package/template/.examples/automation-example.ts

@@ -1,14 +1,8 @@
-import { Client } from "@notionhq/client";
 import { Worker } from "@project-ajax/sdk";
 
 const worker = new Worker();
 export default worker;
 
-// Initialize the Notion client with OAuth token from environment
-const notion = new Client({
-	auth: process.env.NOTION_API_TOKEN,
-});
-
 type RichTextProperty = {
 	type: "rich_text";
 	rich_text: Array<{ plain_text: string }>;
@@ -26,7 +20,8 @@ worker.automation("questionAnswerAutomation", {
 	title: "Question Answer Automation",
 	description:
 		"Reads questions from database pages and updates them with answers",
-	execute: async ({ pageId, pageData }) => {
+	execute: async (event, { notion }) => {
+		const { pageId, pageData } = event;
 		// Extract email from the page dat
 		const emailProperty = pageData?.properties?.Email as
 			| RichTextProperty

package/template/.examples/sync-example.ts

@@ -5,6 +5,41 @@ import * as Schema from "@project-ajax/sdk/schema";
 const worker = new Worker();
 export default worker;
 
+const projectId = "project-1";
+const projectName = "Example Project";
+
+worker.sync("projectsSync", {
+	// Which field to use in each object as the primary key. Must be unique.
+	primaryKeyProperty: "Project ID",
+	// The schema of the collection to create in Notion.
+	schema: {
+		// Name of the collection to create in Notion.
+		defaultName: "Projects",
+		properties: {
+			// See `Schema` for the full list of possible column types.
+			"Project Name": Schema.title(),
+			"Project ID": Schema.richText(),
+		},
+	},
+	execute: async () => {
+		// Fetch and return data
+		return {
+			changes: [
+				// Each change must match the shape of `properties` above.
+				{
+					type: "upsert" as const,
+					key: projectId,
+					properties: {
+						"Project Name": Builder.title(projectName),
+						"Project ID": Builder.richText(projectId),
+					},
+				},
+			],
+			hasMore: false,
+		};
+	},
+});
+
 worker.sync("mySync", {
 	// Which field to use in each object as the primary key. Must be unique.
 	primaryKeyProperty: "ID",
@@ -16,9 +51,10 @@ worker.sync("mySync", {
 			// See `Schema` for the full list of possible column types.
 			Title: Schema.title(),
 			ID: Schema.richText(),
+			Project: Schema.relation("projectsSync"),
 		},
 	},
-	execute: async () => {
+	execute: async (_state, { notion: _notion }) => {
 		// Fetch and return data
 		return {
 			changes: [
@@ -29,6 +65,7 @@ worker.sync("mySync", {
 					properties: {
 						Title: Builder.title("Item 1"),
 						ID: Builder.richText("1"),
+						Project: [Builder.relation(projectId)],
 					},
 				},
 			],

package/template/.examples/tool-example.ts

@@ -41,7 +41,7 @@ worker.tool<
 		additionalProperties: false,
 	},
 	// The function that executes when the tool is called
-	execute: async (input) => {
+	execute: async (input, { notion: _notion }) => {
 		// Destructure input with default values
 		const { query: _query, limit: _limit = 10 } = input;
 

package/template/AGENTS.md

@@ -20,7 +20,7 @@ export default worker;
 worker.sync("tasksSync", {
   primaryKeyProperty: "ID",
   schema: { defaultName: "Tasks", properties: { Name: Schema.title(), ID: Schema.richText() } },
-  execute: async () => ({
+  execute: async (_state, { notion }) => ({
     changes: [{ type: "upsert", key: "1", properties: { Name: Builder.title("Write docs"), ID: Builder.richText("1") } }],
     hasMore: false,
   }),
@@ -30,45 +30,50 @@ worker.tool("sayHello", {
   title: "Say Hello",
   description: "Return a greeting",
   schema: { type: "object", properties: { name: { type: "string" } }, required: ["name"], additionalProperties: false },
-  execute: ({ name }) => `Hello, ${name}`,
+  execute: ({ name }, { notion }) => `Hello, ${name}`,
 });
 
 worker.automation("sendWelcomeEmail", {
   title: "Send Welcome Email",
   description: "Runs from a database automation",
-  execute: async () => {},
+  execute: async (event, { notion }) => {},
 });
 
 worker.oauth("googleAuth", { name: "my-google-auth", provider: "google" });
 ```
 
+- All `execute` handlers receive a Notion SDK client in the second argument as `context.notion`.
+
 - For user-managed OAuth, supply `name`, `authorizationEndpoint`, `tokenEndpoint`, `clientId`, `clientSecret`, and `scope` (optional: `authorizationParams`, `callbackUrl`, `accessTokenExpireMs`).
 
-### Sync Strategy and Pagination
+### Sync
+#### Strategy and Pagination
 
 Syncs run in a "sync cycle": a back-to-back chain of `execute` calls that starts at a scheduled trigger and ends when an execution returns `hasMore: false`.
 
+- Always use pagination, when available. Returning too many changes in one execution will fail. Start with batch sizes of ~100 changes.
+- `mode=replace` is simpler, and fine for smaller syncs (<10k)
+- Use `mode=incremental` when the sync could return a lot of data (>10k), eg for SaaS tools like Salesforce or Stripe
+- When using `mode=incremental`, emit delete markers as needed if easy to do (below)
+
 **Sync strategy (`mode`):**
 - `replace`: each sync cycle must return the full dataset. After the final `hasMore: false`, any records not seen during that cycle are deleted.
-- `incremental`: each sync cycle returns only changes since the last run. Deletions must be explicit via `{ type: "delete", key: "..." }`. Records not mentioned are left unchanged.
-
-**When to use each:**
-- `replace`: small datasets or cheap full scans. Each cycle returns the full dataset for simplicity.
-- `incremental`: large datasets (e.g., Stripe, Salesforce, Zendesk) where full scans are expensive. First backfill, then return only incremental changes.
-
-Implement pagination to avoid exceeding output size limits. Returning too many changes in one execution can cause the output JSON to exceed size limits and fail.
+- `incremental`: each sync cycle returns a subset of the full dataset (usually the changes since the last run). Deletions must be explicit via `{ type: "delete", key: "..." }`. Records not mentioned are left unchanged.
 
 **How pagination works:**
-1. Return a batch of changes with `hasMore: true` and a `nextContext` value
-2. The runtime calls `execute` again with that context
+1. Return a batch of changes with `hasMore: true` and a `nextState` value
+2. The runtime calls `execute` again with that state
 3. Continue until you return `hasMore: false`
 
+**Example replace sync:**
+
 ```ts
 worker.sync("paginatedSync", {
+  mode: "replace",
   primaryKeyProperty: "ID",
   schema: { defaultName: "Records", properties: { Name: Schema.title(), ID: Schema.richText() } },
-  execute: async (context?: { page: number }) => {
-    const page = context?.page ?? 1;
+  execute: async (state, { notion }) => {
+    const page = state?.page ?? 1;
     const pageSize = 100;
     const { items, hasMore } = await fetchPage(page, pageSize);
     return {
@@ -78,34 +83,13 @@ worker.sync("paginatedSync", {
         properties: { Name: Builder.title(item.name), ID: Builder.richText(item.id) },
       })),
       hasMore,
-      nextContext: hasMore ? { page: page + 1 } : undefined,
+      nextState: hasMore ? { page: page + 1 } : undefined,
     };
   },
 });
 ```
 
-**Context types:** The `nextContext` can be any serializable value—a cursor string, page number, timestamp, or complex object. Type your execute function's context parameter to match.
-
-**Replace example (full dataset each cycle, each execute call paginated):**
-```ts
-worker.sync("fullSync", {
-  primaryKeyProperty: "ID",
-  mode: "replace",
-  schema: { defaultName: "Records", properties: { Name: Schema.title(), ID: Schema.richText() } },
-  execute: async (context?: { cursor?: string }) => {
-    const { items, nextCursor } = await fetchPage(context?.cursor);
-    return {
-      changes: items.map((item) => ({
-        type: "upsert",
-        key: item.id,
-        properties: { Name: Builder.title(item.name), ID: Builder.richText(item.id) },
-      })),
-      hasMore: Boolean(nextCursor),
-      nextContext: nextCursor ? { cursor: nextCursor } : undefined,
-    };
-  },
-});
-```
+**State types:** The `nextState` can be any serializable value—a cursor string, page number, timestamp, or complex object. Type your execute function's `state` to match.
 
 **Incremental example (changes only, with deletes):**
 ```ts
@@ -113,8 +97,8 @@ worker.sync("incrementalSync", {
   primaryKeyProperty: "ID",
   mode: "incremental",
   schema: { defaultName: "Records", properties: { Name: Schema.title(), ID: Schema.richText() } },
-  execute: async (context?: { cursor?: string }) => {
-    const { upserts, deletes, nextCursor } = await fetchChanges(context?.cursor);
+  execute: async (state, { notion }) => {
+    const { upserts, deletes, nextCursor } = await fetchChanges(state?.cursor);
     return {
       changes: [
         ...upserts.map((item) => ({
@@ -125,12 +109,54 @@ worker.sync("incrementalSync", {
         ...deletes.map((id) => ({ type: "delete", key: id })),
       ],
       hasMore: Boolean(nextCursor),
-      nextContext: nextCursor ? { cursor: nextCursor } : undefined,
+      nextState: nextCursor ? { cursor: nextCursor } : undefined,
     };
   },
 });
 ```
 
+#### Relations
+
+Two syncs can relate to one another using `Schema.relation(relatedSyncKey)` and `Builder.relation(primaryKey)` entries inside an array.
+
+```ts
+worker.sync("projectsSync", {
+	primaryKeyProperty: "Project ID",
+  ...
+});
+
+// Example sync worker that syncs sample tasks to a database
+worker.sync("tasksSync", {
+	primaryKeyProperty: "Task ID",
+  ...
+	schema: {
+    ...
+		properties: {
+      ...
+			Project: Schema.relation("projectsSync"),
+		},
+	},
+
+	execute: async () => {
+		// Return sample tasks as database entries
+    const tasks = fetchTasks()
+		const changes = tasks.map((task) => ({
+			type: "upsert" as const,
+			key: task.id,
+			properties: {
+        ...
+				Project: [Builder.relation(task.projectId)],
+			},
+		}));
+
+		return {
+			changes,
+			hasMore: false,
+		};
+	},
+});
+```
+
 ## Build, Test, and Development Commands
 - Node >= 22 and npm >= 10.9.2 (see `package.json` engines).
 - `npm run dev`: run `src/index.ts` with live reload.

package/template/CLAUDE.md

@@ -0,0 +1,178 @@
+# Repository Guidelines
+
+## Project Structure & Module Organization
+- `src/index.ts` defines the worker and capabilities.
+- `.examples/` has focused samples (sync, tool, automation, OAuth).
+- Generated: `dist/` build output, `workers.json` CLI config.
+
+## Worker & Capability API (SDK)
+- `@project-ajax/sdk` provides `Worker`, schema helpers, and builders; `@project-ajax/cli` powers `npx workers ...`.
+- Capability keys are unique strings used by the CLI (e.g., `npx workers exec tasksSync`).
+
+```ts
+import { Worker } from "@project-ajax/sdk";
+import * as Builder from "@project-ajax/sdk/builder";
+import * as Schema from "@project-ajax/sdk/schema";
+
+const worker = new Worker();
+export default worker;
+
+worker.sync("tasksSync", {
+  primaryKeyProperty: "ID",
+  schema: { defaultName: "Tasks", properties: { Name: Schema.title(), ID: Schema.richText() } },
+  execute: async (_state, { notion }) => ({
+    changes: [{ type: "upsert", key: "1", properties: { Name: Builder.title("Write docs"), ID: Builder.richText("1") } }],
+    hasMore: false,
+  }),
+});
+
+worker.tool("sayHello", {
+  title: "Say Hello",
+  description: "Return a greeting",
+  schema: { type: "object", properties: { name: { type: "string" } }, required: ["name"], additionalProperties: false },
+  execute: ({ name }, { notion }) => `Hello, ${name}`,
+});
+
+worker.automation("sendWelcomeEmail", {
+  title: "Send Welcome Email",
+  description: "Runs from a database automation",
+  execute: async (event, { notion }) => {},
+});
+
+worker.oauth("googleAuth", { name: "my-google-auth", provider: "google" });
+```
+
+- All `execute` handlers receive a Notion SDK client in the second argument as `context.notion`.
+
+- For user-managed OAuth, supply `name`, `authorizationEndpoint`, `tokenEndpoint`, `clientId`, `clientSecret`, and `scope` (optional: `authorizationParams`, `callbackUrl`, `accessTokenExpireMs`).
+
+### Sync
+#### Strategy and Pagination
+
+Syncs run in a "sync cycle": a back-to-back chain of `execute` calls that starts at a scheduled trigger and ends when an execution returns `hasMore: false`.
+
+- Always use pagination, when available. Returning too many changes in one execution will fail. Start with batch sizes of ~100 changes.
+- `mode=replace` is simpler, and fine for smaller syncs (<10k)
+- Use `mode=incremental` when the sync could return a lot of data (>10k), eg for SaaS tools like Salesforce or Stripe
+- When using `mode=incremental`, emit delete markers as needed if easy to do (below)
+
+**Sync strategy (`mode`):**
+- `replace`: each sync cycle must return the full dataset. After the final `hasMore: false`, any records not seen during that cycle are deleted.
+- `incremental`: each sync cycle returns a subset of the full dataset (usually the changes since the last run). Deletions must be explicit via `{ type: "delete", key: "..." }`. Records not mentioned are left unchanged.
+
+**How pagination works:**
+1. Return a batch of changes with `hasMore: true` and a `nextState` value
+2. The runtime calls `execute` again with that state
+3. Continue until you return `hasMore: false`
+
+**Example replace sync:**
+
+```ts
+worker.sync("paginatedSync", {
+  mode: "replace",
+  primaryKeyProperty: "ID",
+  schema: { defaultName: "Records", properties: { Name: Schema.title(), ID: Schema.richText() } },
+  execute: async (state, { notion }) => {
+    const page = state?.page ?? 1;
+    const pageSize = 100;
+    const { items, hasMore } = await fetchPage(page, pageSize);
+    return {
+      changes: items.map((item) => ({
+        type: "upsert",
+        key: item.id,
+        properties: { Name: Builder.title(item.name), ID: Builder.richText(item.id) },
+      })),
+      hasMore,
+      nextState: hasMore ? { page: page + 1 } : undefined,
+    };
+  },
+});
+```
+
+**State types:** The `nextState` can be any serializable value—a cursor string, page number, timestamp, or complex object. Type your execute function's `state` to match.
+
+**Incremental example (changes only, with deletes):**
+```ts
+worker.sync("incrementalSync", {
+  primaryKeyProperty: "ID",
+  mode: "incremental",
+  schema: { defaultName: "Records", properties: { Name: Schema.title(), ID: Schema.richText() } },
+  execute: async (state, { notion }) => {
+    const { upserts, deletes, nextCursor } = await fetchChanges(state?.cursor);
+    return {
+      changes: [
+        ...upserts.map((item) => ({
+          type: "upsert",
+          key: item.id,
+          properties: { Name: Builder.title(item.name), ID: Builder.richText(item.id) },
+        })),
+        ...deletes.map((id) => ({ type: "delete", key: id })),
+      ],
+      hasMore: Boolean(nextCursor),
+      nextState: nextCursor ? { cursor: nextCursor } : undefined,
+    };
+  },
+});
+```
+
+#### Relations
+
+Two syncs can relate to one another using `Schema.relation(relatedSyncKey)` and `Builder.relation(primaryKey)` entries inside an array.
+
+```ts
+worker.sync("projectsSync", {
+	primaryKeyProperty: "Project ID",
+  ...
+});
+
+// Example sync worker that syncs sample tasks to a database
+worker.sync("tasksSync", {
+	primaryKeyProperty: "Task ID",
+  ...
+	schema: {
+    ...
+		properties: {
+      ...
+			Project: Schema.relation("projectsSync"),
+		},
+	},
+
+	execute: async () => {
+		// Return sample tasks as database entries
+    const tasks = fetchTasks()
+		const changes = tasks.map((task) => ({
+			type: "upsert" as const,
+			key: task.id,
+			properties: {
+        ...
+				Project: [Builder.relation(task.projectId)],
+			},
+		}));
+
+		return {
+			changes,
+			hasMore: false,
+		};
+	},
+});
+```
+
+## Build, Test, and Development Commands
+- Node >= 22 and npm >= 10.9.2 (see `package.json` engines).
+- `npm run dev`: run `src/index.ts` with live reload.
+- `npm run build`: compile TypeScript to `dist/`.
+- `npm run check`: type-check only (no emit).
+- `npx workers auth login [--env=dev]`: connect to a Notion workspace.
+- `npx workers deploy`: build and publish capabilities.
+- `npx workers exec <capability>`: run a sync or tool.
+
+## Coding Style & Naming Conventions
+- TypeScript with `strict` enabled; keep types explicit when shaping I/O.
+- Use tabs for indentation; capability keys in lowerCamelCase.
+
+## Testing Guidelines
+- No test runner configured; validate with `npm run check` and a deploy/exec loop.
+
+## Commit & Pull Request Guidelines
+- Messages typically use `feat(scope): ...`, `TASK-123: ...`, or version bumps.
+- PRs should describe changes, list commands run, and update examples if behavior changes.

package/template/README.md

@@ -22,10 +22,9 @@ npm install
 Connect to a Notion workspace and deploy the sample worker:
 
 ```shell
-npx workers auth login
-# or target a specific environment:
-npx workers auth login --env=dev
 npx workers deploy
+# or target a specific environment:
+npx workers deploy --env=dev
 ```
 
 Run the sample sync to create a database:
@@ -56,6 +55,8 @@ export default worker;
 
 Syncs create or update a Notion database from your source data.
 
+The most basic sync returns all data that should be copied to the Notion database on each run:
+
 ```ts
 import * as Builder from "@project-ajax/sdk/builder";
 import * as Schema from "@project-ajax/sdk/schema";
@@ -72,7 +73,8 @@ worker.sync("tasksSync", {
       ID: Schema.richText(),
     },
   },
-  execute: async () => ({
+  execute: async (_state, { notion }) => ({
+    // `notion` is the Notion API SDK client.
     changes: [
       {
         type: "upsert",
@@ -88,49 +90,49 @@ worker.sync("tasksSync", {
 });
 ```
 
-#### Sync strategy and pagination
-
-A sync runs in a "sync cycle": a back-to-back chain of `execute` calls that ends when an execution returns `hasMore: false`.
+Notion will delete stale rows after each run. A stale row is a row that was in the database but that your function did not return.
 
-Choose a strategy with `mode`:
-- `replace` (default): each cycle returns the full dataset. After the final `hasMore: false`, any records not seen in that cycle are deleted.
-- `incremental`: each cycle returns only changes since the last run. Deletions must be explicit via `{ type: "delete", key: "..." }`. Records not mentioned are left unchanged.
+#### Write a sync that paginates
 
-**When to use each:**
-- `replace`: small datasets or cheap full scans. Each cycle returns the full dataset for simplicity.
-- `incremental`: large datasets (Stripe, Salesforce, Zendesk) where full scans are expensive. First backfill, then return only changes.
+When your sync is pulling in many rows of data (>1k), you'll want to use pagination. Breaking down pages to ~100 is a good starting point.
 
-Paginate large datasets by returning `hasMore: true` with a `nextContext` cursor, and continue until `hasMore: false`.
+You can use `state` to persist things like pagination tokens between `execute` runs. Notion passes `state` as the first argument to `execute`, plus a `context` object that includes the Notion client at `context.notion`. Return `nextState` to set the `state` for the next run:
 
-**Replace example (full dataset each cycle, each execute call paginated):**
 ```ts
 worker.sync("fullSync", {
   primaryKeyProperty: "ID",
   mode: "replace",
   schema: { defaultName: "Records", properties: { Name: Schema.title(), ID: Schema.richText() } },
-  execute: async (context?: { cursor?: string }) => {
-    const { items, nextCursor } = await fetchPage(context?.cursor);
+  execute: async (state, { notion }) => {
+    const { items , nextCursor } = await fetchPage(state?.page);
     return {
       changes: items.map((item) => ({
         type: "upsert",
         key: item.id,
         properties: { Name: Builder.title(item.name), ID: Builder.richText(item.id) },
       })),
-      hasMore: Boolean(nextCursor),
-      nextContext: nextCursor ? { cursor: nextCursor } : undefined,
+      hasMore: nextCursor ? true : false,
+      nextState: nextCursor ? { cursor: nextCursor } : undefined,
     };
   },
 });
 ```
 
-**Incremental example (changes only, with deletes):**
+Return `hasMore=false` for each run until you reach the end. On the last run, return `hasMore=true`. At the start of the next cycle, Notion will start anew and call `execute` with `state` undefined.
+
+#### Write a sync that syncs incrementally
+
+When your sync is working with a lot of data (10k+), you'll want to use the `incremental` sync mode. With incremental syncs, you can for example backfill all the data from an API into Notion, and then sync only incremental updates from that point forward.
+
+Set the sync's `mode` to `incremental` and use pagination as above:
+
 ```ts
 worker.sync("incrementalSync", {
   primaryKeyProperty: "ID",
   mode: "incremental",
   schema: { defaultName: "Records", properties: { Name: Schema.title(), ID: Schema.richText() } },
-  execute: async (context?: { cursor?: string }) => {
-    const { upserts, deletes, nextCursor } = await fetchChanges(context?.cursor);
+  execute: async (state, { notion }) => {
+    const { upserts, deletes, nextCursor } = await fetchChanges(state?.cursor);
     return {
       changes: [
         ...upserts.map((item) => ({
@@ -141,12 +143,34 @@ worker.sync("incrementalSync", {
         ...deletes.map((id) => ({ type: "delete", key: id })),
       ],
       hasMore: Boolean(nextCursor),
-      nextContext: nextCursor ? { cursor: nextCursor } : undefined,
+      nextState: nextCursor ? { cursor: nextCursor } : undefined,
     };
   },
 });
 ```
 
+Unlike the `replace` sync mode, Notion will not drop "stale" rows and `state` will persist between sync cycles.
+
+**Deletes**
+
+With incremental syncs, you can delete rows by returning a delete marker, like so:
+
+```ts
+changes: [
+  // this is an upsert
+  {
+    type: "upsert",
+    key: item.id,
+    properties: { Name: Builder.title(item.name), ID: Builder.richText(item.id) },
+  },
+  // this is a delete
+  {
+    type: "delete",
+    key: item.id
+  }
+]
+```
+
 ### Tool
 
 Tools are callable by Notion custom agents.
@@ -161,7 +185,7 @@ worker.tool("sayHello", {
     required: ["name"],
     additionalProperties: false,
   },
-  execute: ({ name }) => `Hello, ${name}`,
+  execute: ({ name }, { notion }) => `Hello, ${name}`,
 });
 ```
 
@@ -173,7 +197,8 @@ Automations run from Notion database buttons or automations.
 worker.automation("sendWelcomeEmail", {
   title: "Send Welcome Email",
   description: "Runs from a database automation",
-  execute: async ({ pageId }) => {
+  execute: async (event, { notion }) => {
+    const { pageId } = event;
     console.log("Triggered for page", pageId);
   },
 });
@@ -215,6 +240,9 @@ Log in to Notion (use `--env=dev` for dev):
 npx workers auth login --env=dev
 ```
 
+Login is automatically handled by `npx workers deploy`, so this command is
+typically not needed.
+
 ### `npx workers auth show`
 Show the active auth token:
 

package/template/src/index.ts

@@ -5,6 +5,9 @@ import * as Schema from "@project-ajax/sdk/schema";
 const worker = new Worker();
 export default worker;
 
+const projectId = "project-123";
+const projectName = "Project 1";
+
 // Sample data for demonstration
 const sampleTasks = [
 	{
@@ -12,21 +15,52 @@ const sampleTasks = [
 		title: "Welcome to Project Ajax",
 		status: "Completed",
 		description: "This is a simple hello world example",
+		projectId,
 	},
 	{
 		id: "task-2",
 		title: "Build your first worker",
 		status: "In Progress",
 		description: "Create a sync or tool worker",
+		projectId,
 	},
 	{
 		id: "task-3",
 		title: "Deploy to production",
 		status: "Todo",
 		description: "Share your worker with your team",
+		projectId,
 	},
 ];
 
+worker.sync("projectsSync", {
+	primaryKeyProperty: "Project ID",
+	schema: {
+		defaultName: "Projects",
+		databaseIcon: Builder.notionIcon("activity"),
+		properties: {
+			"Project Name": Schema.title(),
+			"Project ID": Schema.richText(),
+		},
+	},
+	execute: async () => {
+		return {
+			changes: [
+				{
+					type: "upsert" as const,
+					key: projectId,
+					icon: Builder.notionIcon("activity"),
+					properties: {
+						"Project Name": Builder.title(projectName),
+						"Project ID": Builder.richText(projectId),
+					},
+				},
+			],
+			hasMore: false,
+		};
+	},
+});
+
 // Example sync worker that syncs sample tasks to a database
 worker.sync("tasksSync", {
 	primaryKeyProperty: "Task ID",
@@ -36,9 +70,9 @@ worker.sync("tasksSync", {
 	schedule: "continuous",
 
 	// Sync mode:
-	// - "replace": Each sync returns the complete dataset. After hasMore:false,
+	// - "replace": Each sync cycle returns the complete dataset. After hasMore:false,
 	//              pages not seen in this sync run are deleted.
-	// - "incremental": Sync returns changes only. Use delete markers
+	// - "incremental": Each sync cycle returns a subset of the complete dataset. Use delete markers
 	//                  (e.g., { type: "delete", key: "task-1" }) to remove pages.
 	// Defaults to "replace".
 	// mode: "replace",
@@ -55,10 +89,11 @@ worker.sync("tasksSync", {
 				{ name: "In Progress", color: "blue" },
 				{ name: "Todo", color: "default" },
 			]),
+			Project: Schema.relation("projectsSync"),
 		},
 	},
 
-	execute: async () => {
+	execute: async (_state, { notion: _notion }) => {
 		const emojiForStatus = (status: string) => {
 			switch (status) {
 				case "Completed":
@@ -81,19 +116,41 @@ worker.sync("tasksSync", {
 				"Task ID": Builder.richText(task.id),
 				Description: Builder.richText(task.description),
 				Status: Builder.select(task.status),
+				Project: [Builder.relation(projectId)],
 			},
 			pageContentMarkdown: `## ${task.title}\n\n${task.description}`,
 		}));
 
 		return {
+			// List of changes to apply to the Notion database.
 			changes,
+			// Indicates whether there is more data to fetch this sync cycle. If true, the runtime will call `execute` again with the nextState.
 			hasMore: false,
+			// Optional state data Notion will pass back as `state`
+			// in the next execution.
+			// This can be any type of data (cursor, page number, timestamp, etc.).
+			nextState: undefined,
 		};
 	},
 });
 
+type TaskSearchInput = {
+	taskId?: string | null;
+	query?: string | null;
+};
+
+type TaskSearchOutput = {
+	count: number;
+	tasks: {
+		id: string;
+		title: string;
+		status: string;
+		description: string;
+	}[];
+};
+
 // Example agent tool for retrieving task information
-worker.tool("taskSearchTool", {
+worker.tool<TaskSearchInput, TaskSearchOutput>("taskSearchTool", {
 	title: "Task Search",
 	description:
 		"Look up sample tasks by ID or keyword. Helpful for demonstrating agent tool calls.",
@@ -115,7 +172,7 @@ worker.tool("taskSearchTool", {
 		required: [],
 		additionalProperties: false,
 	},
-	execute: async (input: { taskId?: string | null; query?: string | null }) => {
+	execute: async (input: TaskSearchInput, { notion: _notion }) => {
 		const { taskId, query } = input;
 
 		let matchingTasks = sampleTasks;
@@ -157,7 +214,7 @@ worker.tool("taskSearchTool", {
 				status: task.status,
 				description: task.description,
 			})),
-		};
+		} satisfies TaskSearchOutput;
 	},
 });
 
@@ -165,7 +222,8 @@ worker.tool("taskSearchTool", {
 worker.automation("completeTaskAutomation", {
 	title: "Mark Task Complete",
 	description: "Automatically marks a task as complete when triggered",
-	execute: async ({ pageId, actionType, pageData }) => {
+	execute: async (event, { notion: _notion }) => {
+		const { pageId, actionType, pageData } = event;
 		// The pageData parameter contains the full page object from Notion's Public API
 		// with all the database properties already encoded and ready to use.