Create a Sync Tag Invalidate Function

Build and deploy a new Sync Tag Invalidate function to Sanity's infrastructure.

Sync Tag Invalidate Functions allow you to run small, single-purpose code whenever your Live Content in Sanity changes. This guide explains how to set up your project, initialize your first blueprint, add a function, and deploy it to Sanity's infrastructure.

Prerequisites:

• The latest version of sanity CLI (sanity@latest) is recommended to interact with Blueprints and Functions as shown in this guide. You can always run the latest CLI commands with npx sanity@latest.
• Node.js v24.x. We highly suggest working on this version as it is the same version that your functions will run when deployed to Sanity.
• An existing project and a role with Deploy Studio permissions (the deployStudio grant).

If you’ve previously created a project, you can skip ahead to Add a Sync Tag Invalidate function.

To create a function, you need to initialize a blueprint. Blueprints are templates that describe Sanity resources. In this case, a blueprint describes how your function will respond to updates in your Sanity project. We recommend keeping functions and blueprints a level above your Studio directory.

For example, if you have a Marketing Website that uses Sanity, you may have a structure like this:

marketing-site/
├─ studio/
├─ next-app/

If you initialize the blueprint in the marketing-site directory, functions and future resources will live alongside the studio and next-app directory.

Initialize your first blueprint with the init command. Replace <project-id> with your project ID, found in manage or your sanity.config.ts file.

npx sanity@latest blueprints init . --type ts --stack-name production --project-id <project-id>

pnpm dlx sanity@latest blueprints init . --type ts --stack-name production --project-id <project-id>

yarn dlx sanity@latest blueprints init . --type ts --stack-name production --project-id <project-id>

bunx sanity@latest blueprints init . --type ts --stack-name production --project-id <project-id>

This configures a new blueprint for your project, adds a sanity.blueprint.ts config file to the current directory (.), and creates a new stack named production.

Follow the prompt and run your package manager’s install command to add the dependencies.

npm install

pnpm install

yarn install

bun install

Use the sanity functions add command to add a new function. You can also run it without any flags for interactive mode.

npx sanity@latest functions add --name invalidate-tags --type sync-tag-invalidate --installer npm

pnpm dlx sanity@latest functions add --name invalidate-tags --type sync-tag-invalidate --installer npm

yarn dlx sanity@latest functions add --name invalidate-tags --type sync-tag-invalidate --installer npm

bunx sanity@latest functions add --name invalidate-tags --type sync-tag-invalidate --installer npm

After running the command, follow the prompt and add the function declaration to your sanity.blueprint.ts configuration. Your file should look like this:

import {defineBlueprint, defineSyncTagInvalidateFunction} from '@sanity/blueprints'

export default defineBlueprint({
  resources: [
    defineSyncTagInvalidateFunction({name: 'invalidate-tags'}),
  ],
})

By default, your new function will receive Live Content sync tag invalidation events for all datasets in your project. We recommend you add an event to your function definition with a resource scoping your function to a particular dataset.

import {defineBlueprint, defineSyncTagInvalidateFunction} from '@sanity/blueprints'

export default defineBlueprint({
  resources: [
    defineSyncTagInvalidateFunction({
      name: "invalidate-tags",
      event: {
        resource: {
          type: 'dataset',
          id: 'myProjectId.myProductionDataset'
        }
      }
    })
  ],
})

You can see all available options in the Function section of the Blueprints configuration reference documentation.

If you've followed the directory structure mentioned earlier, you'll see it grow to something like this:

marketing-site/
├─ studio/
├─ next-app/
├─ sanity.blueprint.ts
├─ package.json
├─ node_modules/
├─ functions/
│  ├─ invalidate-tags/
│  │  ├─ index.ts

After updating the sanity.blueprint.ts file, open functions/invalidate-tags/index.ts in your editor.

Every function exports a handler from the index file.

import { syncTagInvalidateEventHandler } from '@sanity/functions'

export const handler = syncTagInvalidateEventHandler(async ({ context, event, done }) => {
  const time = new Date().toLocaleTimeString()
  console.log(`Your sync tag invalidate Sanity Function was called at ${time}`)
  // TODO: add code to do something with the invalidated sync tags provided to you in `event.data.syncTags`
  try {
    // notify Sanity that you have completed invalidation
    const response = await done(event.data.syncTags)
    console.log('Invalidation complete, Sanity responded with an HTTP', response.status)
  } catch (e) {
    console.error('Error invoking Sanity invalidation done endpoint!', e)
  }
})

import { syncTagInvalidateEventHandler } from '@sanity/functions'

export const handler = syncTagInvalidateEventHandler(async ({ context, event, done }) => {
  const time = new Date().toLocaleTimeString()
  console.log(`Your sync tag invalidate Sanity Function was called at ${time}`)
  // TODO: add code to do something with the invalidated sync tags provided to you in `event.data.syncTags`
  try {
    // notify Sanity that you have completed invalidation
    const response = await done(event.data.syncTags)
    console.log('Invalidation complete, Sanity responded with an HTTP', response.status)
  } catch (e) {
    console.error('Error invoking Sanity invalidation done endpoint!', e)
  }
})

The handler receives a context, an event and a done callback.

The event contains the Live Content sync tags that were invalidated, available at event.data.syncTags. You can learn more in the Function handler reference.

The done callback is an asynchronous method issuing an HTTP request back to Sanity, notifying us that you have completed your invalidation routine. It is a thin wrapper around native node.js fetch, returning a fetch Response.

You can test functions locally with the functions development playground. Local testing is a great way to experiment without affecting your usage quota.

To launch the development playground, run the following:

npx sanity functions dev

pnpm dlx sanity functions dev

yarn dlx sanity functions dev

bunx sanity functions dev

If you run this on the starter function from earlier, you'll see the default output message in the console pane.

Select your new Sync Tag Invalidate function from the list on the left. Note that the Sync Tag Payload panel is populated with a dummy sync tag invalidate event shape that your function can use as a test payload.

Click the Run button at the bottom, and you should see the starter Sync Tag Invalidate function template code output its logs to the Console panel:

4/10/2026 9:14:52 AM INFO Your sync tag invalidate Sanity Function was called at 9:14:52 AM
4/10/2026 9:14:52 AM INFO Invalidation complete, Sanity responded with an HTTP 204

Once you're satisfied that the function works as expected, deploy it by deploying the blueprint stack.

npx sanity blueprints deploy

pnpm dlx sanity blueprints deploy

yarn dlx sanity blueprints deploy

bunx sanity blueprints deploy

You can begin using your function when the deployment finishes. Edit a document in a dataset and publish the changes to trigger the function.

If you need to change the function, update your code and re-run the deploy command to push the new changes live.

When you tested the function locally, you saw the logs directly in your console. Once deployed, the function and its logs are in the cloud.

View the logs with the functions logs command. Replace invalidate-tags with your function name.

npx sanity functions logs invalidate-tags

pnpm dlx sanity functions logs invalidate-tags

yarn dlx sanity functions logs invalidate-tags

bunx sanity functions logs invalidate-tags

This command outputs the function's logs. Try updating your document, publishing the change, and running the command again to see new logs.

Sometimes you want to remove a deployed resource so it won't run anymore or affect any future usage quotas.

To remove a resources created with a blueprint, you need to either:

• Remove the definition from the blueprint, and run the deploy command again.
• Destroy the blueprint with the destroy command.

The blueprints destroy command removes, or undeploys, the blueprint and all of its resources from Sanity's infrastructure. It does not remove your local files.

npx sanity blueprints destroy

pnpm dlx sanity blueprints destroy

yarn dlx sanity blueprints destroy

bunx sanity blueprints destroy

To remove the resource from the blueprint locally, you can remove it from the resources array in the sanity.blueprint.ts file, then delete any associated files.

When you run blueprints destroy, it's as if you never used blueprints init during setup. The only difference is you still have all the files in your directory. To use this blueprint again and redeploy it, you'll need to let Sanity know about it. You can do this by running init again:

npx sanity blueprints init

pnpm dlx sanity blueprints init

yarn dlx sanity blueprints init

bunx sanity blueprints init

This launches an editing interface that lets you reconfigure the blueprint, if needed, and it reconnects the blueprint to Sanity. Now you can add more functions or redeploy. Keep in mind that any environment variables added before destroying the blueprint will not carry over.