Mattering Automations Vercel integration
Connect Vercel to Mattering Automations: deployments, promote and rollback, environment variables, domains and Vercel DNS, aliases, Global Config, and webhook management as workflow steps, authenticated with a Vercel access token.
The Mattering Automations Vercel integration puts Vercel on your automation canvas: create and watch deployments, promote a deployment to production for instant rollback, manage environment variables, attach and verify domains, edit Vercel DNS records, switch aliases between deployments, read and write Global Config items, and manage webhooks. Because the nodes live on the same canvas as every other connector, a failed build can open a task in Mattering Productivity, a content change in another system can trigger a redeploy, and an incident workflow can flip a feature flag and roll production back in the same run.
Setup takes a few minutes: create an access token in the Vercel dashboard, attach it as a credential in Mattering, and test the connection. Two Vercel-specific mechanics are handled for you. Vercel versions each endpoint individually rather than the API as a whole, and every node pins the exact version prefix from Vercel's published OpenAPI document, so an endpoint revision cannot shift under your workflows. And team-owned resources are addressed by a teamId query parameter, which the integration models as an optional teamId field on 48 of the 50 nodes; without it, requests run against the token owner's personal account.
The risk map is small and explicit. Five nodes permanently destroy data: Vercel: Delete Project, Vercel: Delete Deployment, Vercel: Delete Domain, Vercel: Delete DNS Record, and Vercel: Delete Environment Variable. The production traffic moves, Vercel: Promote Deployment to Production and Vercel: Assign Alias to Deployment, are reversible by pointing back at the previous deployment. Registrar purchases, renewals, and transfers are deliberately not on the canvas because they charge real money; Vercel: Check Domain Availability remains because checking is free. This guide walks through setup, the working patterns, and ends with the full node reference.
Before you start
- A Vercel account. The free Hobby plan can create access tokens and is enough to evaluate every node, but Vercel's fair use guidelines restrict Hobby to personal, non-commercial use, so automations for a business or client belong on a paid Vercel plan.
- Access to create a token in the Vercel dashboard, and for team resources, membership in the team the token will be scoped to.
- A Mattering workspace with access to the Automations app.
- For the deployment nodes: a project with a linked git repository or at least one existing deployment, because Vercel: Create Deployment deploys a commit from the linked repository or redeploys a previous deployment; it does not accept raw file uploads.
Create a Vercel access token
Mattering authenticates to Vercel with a personal access token sent as a standard Bearer authorization header, which the integration builds for you. Tokens are created in the Vercel dashboard and scoped at creation to your full account, a single team, or a single project, with an optional expiration date.
Connect Vercel to Mattering
Verify it works
After connecting, open any automation canvas and check the palette: a Vercel section should list the query and action nodes. Drop Vercel: Get Current User onto the canvas and run a test step; it needs no configuration and returns the account's id, email, username, and plan. Then run Vercel: List Projects, which returns projects newest-updated first with their framework and latest deployments; project ids and names from this list are the inputs most other nodes want.
If you work in a team, run Vercel: List Teams next. It returns each team's id, and that id is exactly what the optional teamId field on the other Vercel nodes expects. This is worth verifying early because it is the most common stumble: without teamId, every request runs against your personal account, so a team-owned project simply does not appear in Vercel: List Projects and lookups against it return 404.
Node reference
50 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 27
Vercel: Check Domain Availability
vercel_check_domain_availability
Check whether a domain name is available to register, via Vercel's registrar. A free read: it checks availability only and never purchases anything.
Vercel: Get Alias
vercel_get_alias
Get one alias by its ID or hostname, including which deployment it currently points at.
Vercel: Get Current User
vercel_get_current_user
Return the user the access token belongs to: id, email, username, and plan. Free and parameterless, so it doubles as the credential health check: a bad token gets a 403, a good one identifies the account.
Vercel: Get Deployment
vercel_get_deployment
Get one deployment's full record by ID or URL hostname: build state, aliases, target environment, regions, timings, and creator. Poll this after a redeploy to wait for readyState READY or ERROR.
Vercel: Get Domain
vercel_get_domain
Get one account domain's record: nameservers (actual and intended), registrar service type, expiry, and verification status.
Vercel: Get Domain Configuration
vercel_get_domain_config
Check how a domain is configured for Vercel: whether its DNS is misconfigured, which nameservers it uses, and whether it is served by Vercel's edge. The go-to diagnostic when a domain will not verify.
Vercel: Get Environment Variable
vercel_get_env_var
Get one environment variable by its ID, with the DECRYPTED value for plain and encrypted types (sensitive-type values cannot be read back). The value lands in the execution record, so wire it straight where it is needed.
Vercel: Get Global Config
vercel_get_edge_config
Get one Global Config's metadata by ID: slug, owner, digest, size, and item count (not the items themselves).
Vercel: Get Project
vercel_get_project
Get one project's full record by ID or name: build settings, framework, git link, production target, and latest deployments.
Vercel: Get Team
vercel_get_team
Get one team's full record by its team ID: slug, name, creation date, and the requesting user's membership.
Vercel: Get Webhook
vercel_get_webhook
Get one webhook's configuration by ID: URL, events, and project scope (never the signing secret).
Vercel: List Aliases
vercel_list_aliases
List the aliases (custom URLs pointing at deployments) on the account, optionally filtered to one project or domain.
Vercel: List Auth Tokens
vercel_list_auth_tokens
List the metadata of all access tokens on the authenticated account: name, creation time, expiry, and scopes. Token VALUES are never returned (they are shown once at creation only), so this is a safe audit read.
Vercel: List DNS Records
vercel_list_dns_records
List the DNS records of a domain that uses Vercel DNS, with each record's id, type, name, value, and TTL.
Vercel: List Deployment Checks
vercel_list_deployment_checks
List the checks registered on a deployment by integrations (end-to-end tests, Lighthouse-style audits) with status, conclusion, and metrics. Read-only: creating checks requires an integration installation, not an access token.
Vercel: List Deployment Events
vercel_list_deployment_events
Fetch a deployment's build log events (stdout, stderr, and lifecycle messages) as JSON, for build-failure diagnostics. Returns a bounded page; live following is not supported on the canvas.
Vercel: List Deployment Files
vercel_list_deployment_files
List the source file tree of a deployment as nested directory/file entries with file IDs. Works for deployments created with uploaded sources; git-built deployments may return 404 because their sources live in the repository.
Vercel: List Deployments
vercel_list_deployments
List deployments across the account or filtered to one project, environment, state, or branch, newest first. Each item carries the deployment uid needed by the other deployment nodes.
Vercel: List Domains
vercel_list_domains
List the domains registered to the account or team, with nameserver status, expiry, and verification state.
Vercel: List Environment Variables
vercel_list_env_vars
List a project's environment variables with key, target environments, type, and metadata. Values come back encrypted unless decrypt=true; variables of type sensitive never return their value at all.
Vercel: List Global Config Items
vercel_list_edge_config_items
Read all key-value items in a Global Config: feature flags, settings, allowlists. Reads are metered on paid usage but free-tier Hobby includes 100K reads per month.
Vercel: List Global Configs
vercel_list_edge_configs
List the account's Global Configs (the key-value stores formerly named Edge Config) with id, slug, size, and item count.
Vercel: List Project Domains
vercel_list_project_domains
List the domains attached to a project with their git branch, redirect target, and verification status.
Vercel: List Projects
vercel_list_projects
List projects in the personal account or a team, newest-updated first, with framework, git link, and latest deployments. Page with the from field using data.pagination.next from the previous response.
Vercel: List Team Members
vercel_list_team_members
List the members of a team with their role, email, username, and join date. Supports searching by name or email and filtering by role.
Vercel: List Teams
vercel_list_teams
List every team the token's user belongs to, with each team's id, slug, name, and the user's role. The team id here is what the teamId field on the other Vercel nodes expects.
Vercel: List Webhooks
vercel_list_webhooks
List the account's webhooks with their target URL, subscribed events, and project scope. Signing secrets are not included (they are returned once at creation).
Action nodes 23
Vercel: Add Domain
vercel_add_domain
Register an EXISTING domain you already own with the Vercel platform (method add), so it can be attached to projects and managed via Vercel DNS. This never buys a domain and incurs no charge; purchase and transfer-in are deliberately not on the canvas.
Vercel: Add Domain to Project
vercel_add_project_domain
Attach a domain to a project, optionally scoped to a git branch or set up as a redirect to another of the project's domains. If the domain's DNS is not pointed at Vercel yet, the response includes verification instructions and verified stays false until DNS checks pass.
Vercel: Assign Alias to Deployment
vercel_assign_alias
Point an alias hostname at a specific deployment. If the alias already exists it is atomically switched over (the manual blue-green / rollback move); assigning it back to the previous deployment reverses it. The hostname must be a domain on the account or a *.vercel.app name you control.
Vercel: Cancel Deployment
vercel_cancel_deployment
Cancel a deployment that is still queued or building. The deployment ends in state CANCELED; production keeps serving whatever was live before. A finished deployment cannot be canceled (redeploy or promote another instead).
Vercel: Create DNS Record
vercel_create_dns_record
Add a DNS record to a domain on Vercel DNS: A, AAAA, ALIAS, CAA, CNAME, HTTPS, MX, SRV, TXT, or NS. The API validates the value against the type (an A record needs an IPv4 address, and so on) and rejects fields that do not belong to the chosen type.
Vercel: Create Deployment
vercel_create_deployment
Create a deployment from existing sources: redeploy a previous deployment (deploymentId) or deploy a commit from the project's linked git repository (gitSource). Consumes build minutes and counts against the deployments-per-day limit (100/day on Hobby); target=production ships to the production URL once ready. From-scratch file uploads are not supported on the canvas.
Vercel: Create Environment Variable
vercel_create_env_var
Add an environment variable to a project for one or more target environments. Existing deployments are unaffected; the new value applies from the next deployment. Set upsert=true to overwrite an existing variable with the same key and target instead of failing.
Vercel: Create Project
vercel_create_project
Create a new project, optionally linked to a git repository and pre-seeded with environment variables. Creating a project does not deploy anything by itself; a linked repository deploys on its next push.
Vercel: Create Webhook
vercel_create_webhook
Create a webhook that POSTs platform events (deployment created/succeeded/error, project created, domain created, and more) to your URL. The response includes the signing secret EXACTLY ONCE: store it immediately, it cannot be fetched again.
Vercel: Delete Alias
vercel_delete_alias
Delete an alias by ID or hostname. Traffic to that hostname stops resolving to the deployment immediately; re-assigning the same hostname restores it. Mind that deleting a live production alias takes that URL offline until reassigned.
Vercel: Delete DNS Record
vercel_delete_dns_record
Delete a DNS record from a domain on Vercel DNS. Whatever the record pointed at (mail routing, a subdomain, a verification TXT) stops resolving as caches expire, and the API has no undo: recreate the record to restore it.
Vercel: Delete Deployment
vercel_delete_deployment
Permanently delete a deployment by ID (or by URL via the url field, which then takes precedence). Its unique URL stops serving and its build logs go with it; there is no undelete on the API. Deleting the current production deployment takes the production site down until another is promoted.
Vercel: Delete Domain
vercel_delete_domain
Remove a domain from the Vercel account entirely. Its Vercel-DNS records and project attachments stop working immediately and the records are not recoverable (re-adding the domain starts from scratch). Ownership at the registrar is unaffected.
Vercel: Delete Environment Variable
vercel_delete_env_var
Delete an environment variable by ID. The stored value is gone for good (and a sensitive-type value was never readable), so capture it first if you might need it back. Existing deployments keep running with the value they were built with.
Vercel: Delete Project
vercel_delete_project
Permanently delete a project by ID or name, including its deployments, environment variables, and domain attachments. There is no undo on the API: the project and its deployment history are gone. Returns 204 with an empty body on success.
Vercel: Delete Webhook
vercel_delete_webhook
Delete a webhook by ID; deliveries stop immediately. Recreating it later issues a NEW signing secret, so the receiver's verification key must be updated too. Returns 204 with an empty body.
Vercel: Promote Deployment to Production
vercel_promote_deployment
Point production traffic at an existing successful deployment (staged promote / instant rollback pattern). Production domains switch to this deployment without a rebuild; promoting the previous deployment again reverses it. Returns 201 with an empty body; the switch itself completes asynchronously.
Vercel: Remove Domain from Project
vercel_remove_project_domain
Detach a domain from a project. The domain itself stays on the account (this is not domain deletion) and can be re-attached, but traffic to it stops resolving to this project immediately.
Vercel: Update DNS Record
vercel_update_dns_record
Edit an existing DNS record by its record ID. Only the fields you fill are sent. DNS caches mean changes take up to the old TTL to propagate.
Vercel: Update Environment Variable
vercel_update_env_var
Edit an existing environment variable by ID. Only the fields you fill are sent, so an update can change just the value while keeping key, type, and targets. Applies from the next deployment.
Vercel: Update Global Config Items
vercel_update_edge_config_items
Batch upsert or delete key-value items in a Global Config (flip feature flags, update settings). Changes propagate to reads within seconds. Writes are metered and rate-limited: Hobby includes 100 writes per month (then 250/month hard cap), paid plans 100 writes per hour.
Vercel: Update Project
vercel_update_project
Update a project's settings. Only the fields you fill are sent, so untouched settings keep their values. Build-setting changes apply from the next deployment onward.
Vercel: Verify Project Domain
vercel_verify_project_domain
Trigger a verification check for a project domain that is pending verification (after adding the TXT record or pointing DNS). Returns the domain with its updated verified flag and any still-missing verification steps.
Using the integration
On the automation canvas
Vercel nodes chain with every other node, which is the reason to run Vercel here rather than in isolation. A scheduled Vercel: List Deployments filtered to state ERROR can open a task in Mattering Productivity with the build log from Vercel: List Deployment Events attached, a record changing in your CRM or CMS can trigger Vercel: Create Deployment to rebuild a site, and an incident workflow can flip a flag off with Vercel: Update Global Config Items and roll production back in the same run. Approvals, run history, and retries are the platform's, not something you build per integration.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter can list deployments, read build logs, and check domain configuration through the same nodes your workflows use. Vercel also operates its own official MCP server at mcp.vercel.com, with OAuth sign-in and tools for documentation search, project and deployment management, log analysis, and Web Analytics; if you only want an assistant talking to Vercel alone, that is a reasonable option. What this integration adds is Vercel sitting beside every other connector in one workflow, plus write surfaces like DNS records, environment variables, aliases, and Global Config items. Either way, the read nodes are the safe surface for an agent: keep the five delete nodes and production traffic moves behind an approval step.
Deploy, watch, promote
The reliable release pattern uses four nodes. Before shipping, Vercel: List Deployments filtered to READY production deployments records the current deployment's uid as the rollback target. Vercel: Create Deployment then deploys a commit from the linked repository or redeploys an existing deployment by id, with target production sending it to the production URL once ready. Vercel: Get Deployment polls until readyState is READY or ERROR, and every downstream step should branch on that. If the release goes wrong, Vercel: Promote Deployment to Production points production back at the saved uid without a rebuild; promoting is also how you roll forward to any other successful deployment. Vercel: Cancel Deployment only works while a build is queued or building, and production keeps serving whatever was live, so it is a cleanup tool, not a rollback.
Team scope and teamId
Vercel separates your personal account from teams, and the token plus the teamId field decide which one a node talks to. A request without teamId runs against the token owner's personal account; passing the team id from Vercel: List Teams addresses the team's resources instead. 48 of the 50 nodes accept teamId; the two identity reads are inherently personal. The token's own scope sits above all of this: Full Account tokens need teamId to address a team, while team-scoped and project-scoped tokens do not require teamId at all (Vercel infers it) and answer 403 for anything outside their scope. When a workflow will only ever serve one team, set teamId once per node and scope the token to that team so a mistake fails loudly instead of quietly running against the wrong account.
Domains and DNS end to end
Vercel: Add Domain registers a domain you already own with the platform, and Vercel: Add Domain to Project attaches it to a project, returning verification instructions when DNS is not yet pointed at Vercel. Vercel: Verify Project Domain retriggers the check after you add the TXT record or repoint DNS, and Vercel: Get Domain Configuration is the diagnostic for a domain that will not verify, reporting whether DNS is misconfigured and which nameservers are actually in use. For domains on Vercel DNS, Vercel: List DNS Records, Vercel: Create DNS Record, Vercel: Update DNS Record, and Vercel: Delete DNS Record manage records directly, with the API validating each value against its record type. One canvas quirk: a record on the root domain needs an empty name, which a blank field cannot express, so the create node documents an extra_body override for it. Registrar purchases and transfers are deliberately absent; Vercel: Check Domain Availability is a free read and never buys anything.
Environment variables and Global Config
Vercel: List Environment Variables returns a project's variables with values encrypted unless you ask for decryption, and Vercel: Get Environment Variable reads one decrypted value by id; variables created with the sensitive type are write-only by design and never return their value to anyone. Writes follow deployment semantics: Vercel: Create Environment Variable (with upsert to overwrite by key) and Vercel: Update Environment Variable change what the next deployment sees, while existing deployments keep the values they were built with, so chain a redeploy when the change must take effect now. Global Config is the opposite: Vercel: Update Global Config Items batch-writes key-value items that propagate to reads within seconds, no deploy involved, which is why it suits feature flags and kill switches. Its writes are metered per plan, so schedule flag flips rather than looping them, and read the current items first with Vercel: List Global Config Items.
Troubleshooting
Test Connection fails with a 403
Test Connection passes but a node returns 403
A project I can see in the dashboard returns 404, or List Projects seems incomplete
Requests start failing with 429 rate-limit errors
Create Deployment is rejected or seems to want files
An environment variable read comes back encrypted or with no value
A domain stays unverified after adding it to a project
Creating a DNS record for the root domain fails
Global Config writes start failing partway through the month
Related
The Vercel MCP
What connecting Vercel unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Vercel is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.