Menu
Mattering Automations connector

An Upstash MCP for the management API: databases, indexes, backups and teams

Connect your Upstash account email and a management API key, and 37 nodes land on the canvas: create and configure Redis databases, take and restore backups, create and transfer Vector indexes, set budgets and read regions, manage teams and members, and read the audit trail. Provisioning and hygiene that used to be console clicks, running on a schedule or from an AI assistant.

37 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Upstash MCP connector does

The Upstash connector for Mattering Automations is 37 nodes on the Upstash Developer API, which is the entire documented surface of that API: Redis databases (16 nodes), Redis backups (6), teams (6), Vector indexes (8) and the account audit log. It provisions, configures and audits Upstash resources from a workflow, and it is honest about being one plane rather than four.

Read this boundary before anything else, because it decides whether this connector is the right tool. Upstash ships four HTTP APIs and no two of them share a credential: the Developer API on api.upstash.com, the Redis REST API on each database's own host with that one database's token, the Vector REST API on each index's own host with that index's token, and QStash with its own token. This connector builds the Developer API and nothing else. So it manages Redis databases and Vector indexes; it does not read or write Redis keys, does not upsert or query vectors, and does not publish QStash messages. The Developer API has no QStash surface at all, and no Kafka section either, so nothing here manages those.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can create a Redis database for a new environment, set its budget and read regions, take a backup before a risky change, and write the endpoint host into a Mattering database, without anyone opening the Upstash console.

Upstash publishes MCP servers of its own, and they are worth knowing about before you choose. Upstash ships a Redis MCP server built for the data plane, whose tools run Redis commands against a database and search the Upstash documentation, and a broader Upstash MCP for account-level work including creating databases and reading QStash and Workflow logs. If what you want is an agent that runs Redis commands against your keys, that is the vendor's server and this connector cannot do it, because it never touches a database host. What this connector adds is the management surface in full, including the parts their server does not cover, such as Vector index lifecycle, backups and restores, teams and membership, budgets and read regions, and the audit log, delivered as canvas steps that run on a schedule or a trigger with nobody present, chain with every other connector in one workflow, hold the key in a shared workspace credential store rather than in an individual's config, and carry destructive flags you can gate on.

The safety modeling is stated rather than implied, and the seven destructive nodes split into two kinds that should never be conflated. Data is destroyed by Upstash: Delete Redis Database, Upstash: Delete Vector Index, Upstash: Delete Redis Backup, Upstash: Restore Redis Backup and Upstash: Delete Team. No data at all is touched by Upstash: Reset Redis Password and Upstash: Reset Vector Index Tokens, which instead break every live client the instant they return, with no grace period and no way back to the old values. The restore node deserves its own line: Upstash's own backup documentation states that all existing data in the target database is deleted before the restore begins, so a restore is a destructive write to the target, not an additive one.

One connection, three surfaces

  • Visual automations. Drag Upstash nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Upstash node, ready to drop on the canvas

37 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 9

Upstash: Get Redis Database

Get one Redis database's full configuration: name, region, state, endpoint host, port, plan type, budget, read regions, eviction and TLS settings, and its current limits. By default the response also carries the database's LIVE connection credentials, so treat this node's output as secret material or set the credentials field to hide.

Upstash: Get Redis Database Stats

Read usage and performance metrics for one Redis database: daily read and write request counts, connection count, keyspace size, throughput, disk usage, mean and 99th percentile latency, monthly bandwidth, monthly request count and month-to-date billing. The time-series fields are arrays of {x, y} points where x is a timestamp string. The window is fixed by Upstash and takes no parameters, so this node declares no incremental window.

Upstash: Get Team Members

List the members of one team, each with their email address and role (owner, admin, dev or finance). The response is a bare JSON array, so paths read data[].member_email.

Upstash: Get Vector Index

Get one Vector index's configuration: name, region, similarity function, dimension count, embedding model, index type, plan and limits, plus its endpoint host. The response carries the index's live data-plane token, so treat the output as secret material.

Upstash: List Audit Logs

Read the account's audit trail: who did what, when, from which IP, and through which client. Each entry carries the actor's email, a human-readable action string, the affected entity, and the source, which distinguishes a console action from an API-key one. The response is a bare JSON array, so paths read data[].action_string. This is the node to build a change-alerting workflow on. Upstash documents no parameters for it, so there is no filtering or paging here; use extra_query if the vendor adds some.

Upstash: List Redis Backups

List the backups taken from one Redis database, each with its backup id, name, creation time, state and size. The response is a bare JSON array, so paths read data[].backup_id. This is what the backup picker on the restore and delete nodes reads from.

Upstash: List Redis Databases

List every Upstash Redis database on the account, with each one's id, name, region, plan type, state, endpoint host and current limits. The response is a bare JSON array, so paths read data[].database_id. This is the node every other Redis node's database picker reads from, and it is also the cheapest way to confirm a credential works.

Upstash: List Teams

List every team the account belongs to, with each team's id and name. The response is a bare JSON array, so paths read data[].team_id. This is what the team picker on the membership, move-to-team and index-transfer nodes reads from.

Upstash: List Vector Indexes

List every Upstash Vector index on the account, with each one's id, name, region, similarity function, dimension count, embedding models, index type, plan and limits. The response is a bare JSON array, so paths read data[].id. It also carries each index's LIVE data-plane token and read-only token, so treat this node's output as secret material. This is what the index picker on the other Vector nodes reads from.

Action nodes 28

Upstash: Add Team Member

Add a person to a team by email address and give them a role. They gain access to everything the team owns as soon as this returns, so treat the role as an access-control decision rather than a label.

Upstash: Change Redis Plan

Move a Redis database onto a different plan. This changes what the account is billed, immediately. It is reversible in the sense that the plan can be changed back, but money already spent is not returned by changing it back. Moving DOWN to a smaller fixed plan can fail if the database already holds more data than the target allows. Returns the string OK.

Upstash: Create Redis Backup

Take a point-in-time backup of a Redis database. This is the only thing that makes Upstash: Delete Redis Database recoverable, so run it before any bulk rewrite or teardown. The call returns the string OK and no backup id: read Upstash: List Redis Backups afterwards to find the new backup and watch its state reach completed.

Upstash: Create Redis Database

Create a new Upstash Redis database. The response carries the new database's id and its endpoint host, and by default its live connection credentials as well, so treat the output as secret material. Choosing a paid plan starts billing immediately.

Upstash: Create Team

Create a team. Teams own databases and indexes separately from the personal account, which is how access and billing are shared. The response carries the new team id.

Upstash: Create Vector Index

Create an Upstash Vector index. The similarity function and dimension count are fixed at creation and decide what embeddings the index can ever hold, so they must match whatever produces your vectors. The response carries the new index's endpoint host and its live data-plane token, which is what the Vector REST API needs - this connector manages indexes and does not read or write vectors itself.

Upstash: Delete Redis Backup

DESTRUCTIVE AND IRREVERSIBLE. Delete one backup. The database and its live data are untouched; what is lost is a restore point, which matters most in exactly the situation a backup exists for. Other backups of the same database survive. Returns the string OK.

Upstash: Delete Redis Database

DESTRUCTIVE AND IRREVERSIBLE. Delete a Redis database and every key stored in it. The endpoint host stops resolving and every client using it fails. There is no trash and no undo: the only recovery is a backup taken beforehand with Upstash: Create Redis Backup, and a backup is destroyed along with its database. Backups of OTHER databases and the rest of the account are unaffected. Returns the string OK.

Upstash: Delete Team

DESTRUCTIVE AND IRREVERSIBLE. Delete a team. Every member loses access through it and the team's billing arrangement goes with it. Move any database or index the team owns out first - Upstash: Move Redis Database To Team and Upstash: Transfer Vector Index move resources between owners. Returns the string OK.

Upstash: Delete Vector Index

DESTRUCTIVE AND IRREVERSIBLE. Delete a Vector index and every vector and piece of metadata in it. The endpoint host stops resolving. Upstash Vector has no backup endpoint in the developer API, so unlike a Redis database there is no restore point to fall back on: the only recovery is re-embedding and re-upserting the source data. Other indexes are unaffected. Returns the string OK.

Upstash: Disable Redis Auto Upgrade

Stop Upstash moving this database to a larger plan on its own. Spend stops growing unattended; in exchange, the database starts rejecting writes once it reaches the limits of its current plan. Any upgrade already applied stays applied. Returns the string OK.

Upstash: Disable Redis Daily Backup

Turn off automatic daily backups for a Redis database. No further automatic backups are taken; backups already on the account are not deleted by this call. Returns the string OK.

Upstash: Disable Redis Eviction

Stop the database evicting keys when it fills up. Nothing is restored, and once the size limit is reached new writes are rejected rather than making room. Returns the string OK.

Upstash: Enable Redis Auto Upgrade

Let Upstash move this database to a larger plan on its own when it outgrows the current one, rather than rejecting writes. This is a BILLING setting: an upgrade it performs raises the bill without asking. Reverse it with Upstash: Disable Redis Auto Upgrade. Returns the string OK. (The vendor's reference files this page under the name autoscaling; the endpoint is autoupgrade and this is what it does.)

Upstash: Enable Redis Daily Backup

Turn on automatic daily backups for a Redis database. Upstash then takes and retains them on its own schedule; retention is a console setting rather than a parameter here. Returns the string OK.

Upstash: Enable Redis Eviction

Let the database evict old keys when it reaches its size limit, instead of rejecting new writes. The setting itself is reversible, but keys evicted while it is on are gone for good, so this is a cache setting and not a storage one. Returns the string OK.

Upstash: Enable Redis TLS

Require TLS on connections to this Redis database. ONE WAY: the developer API documents no disable-TLS endpoint, so this cannot be undone here. Any client still connecting without TLS will need reconfiguring. Returns the updated database object.

Upstash: Move Redis Database To Team

Move a Redis database from the personal account into a team, transferring ownership and billing with it. The database keeps its id, endpoint host and credentials, so nothing connected to it breaks. Everyone in the target team gains access according to their role. Returns the string OK.

Upstash: Remove Team Member

Remove a person from a team. Their access to everything the team owns ends immediately. Nothing is deleted and the person can be added back with Upstash: Add Team Member, which is why this is a reversible write rather than a destructive one - but note that the request body carries the team and the email only, so removing the wrong person is a single wrong picker selection away. Returns the string OK.

Upstash: Rename Redis Database

Change a Redis database's display name. This is a label only: the database id, the endpoint host and the connection credentials are all unchanged, so nothing connected to it breaks. Returns the updated database object.

Upstash: Rename Vector Index

Change a Vector index's display name. A label only: the index id, the endpoint host and the tokens are unchanged, so nothing connected to it breaks. Returns the string OK.

Upstash: Reset Redis Password

DESTRUCTIVE TO EVERY LIVE CLIENT. Rotate the database's password and REST token. No data is deleted and no key is touched, but every application, worker, cron job and deployed environment variable holding the previous credential stops authenticating the moment this returns, and the old value cannot be restored. Run it only when you are ready to redeploy the new credential everywhere. The new credentials come back in the response, which is therefore secret material.

Upstash: Reset Vector Index Tokens

DESTRUCTIVE TO EVERY LIVE CLIENT. Rotate the index's data-plane token AND its read-only token together. No vector is deleted and the index keeps its id, name and endpoint host, but every application holding either old token stops authenticating the moment this returns, and the old values cannot be recovered. Read the new ones back with Upstash: Get Vector Index. Returns the string OK, not the new tokens.

Upstash: Restore Redis Backup

DESTRUCTIVE TO THE TARGET DATABASE. Restore a backup into a database. Upstash's own documentation states that all existing data in the target database is deleted before the restore begins, so anything written since the backup was taken is lost unless a second backup was taken first. The backup itself is not consumed and stays available, and other databases are untouched. The database id, endpoint host and credentials do not change, so clients stay connected - they simply see different data. Returns the string OK.

Upstash: Set Vector Index Plan

Move a Vector index onto a different plan. This changes what the account is billed, immediately. Reversible in that the plan can be changed back; money already spent is not returned by changing it back. Returns the string OK.

Upstash: Transfer Vector Index

Move a Vector index to a team, transferring ownership and billing with it. The index keeps its id, endpoint host and tokens, so nothing connected to it breaks, and everyone in the target team gains access. ONE WAY in practice: Upstash states that transferring to a personal account is not supported, so an index moved into a team cannot be moved back out through this API. Returns the string OK.

Upstash: Update Redis Budget

Set the monthly spend ceiling for one Redis database. This is the guard rail on usage-based charges, so setting it too low can stop a database serving once it is reached. Returns the string OK.

Upstash: Update Redis Read Regions

Replace the set of read regions for a global Redis database. The list is a REPLACEMENT, not an addition: any region you leave out is removed, and its read replica goes with it. The primary region is set at creation and is not changed here. Adding regions adds cost. Returns the string OK.

Connecting Upstash takes one credential

Upstash authenticates the Developer API with HTTP Basic where the username is your account email address and the password is a management API key, created in the Upstash console under Account and then Management API. Mattering ships a dedicated credential form with those two labels rather than a generic username and password pair, because a form labelled Password invites the console password, which is not what this API wants. There is a hard access condition to check first, and it is invisible from inside the product: Upstash documents the Developer API as available only to native Upstash accounts, and states that accounts created through third-party platforms such as Vercel or Fly.io are not supported. Someone who provisioned Upstash through a marketplace has a working console, working databases and working data-plane tokens, and simply no Management API page to create a key on, with no error anywhere explaining why. The only fix is a native Upstash account. Two more key facts worth knowing before you create one: Upstash states that it does not keep your API key, so a forgotten key is replaced rather than recovered, and role-based access for keys is on the vendor's roadmap rather than available, which means every management key today is a full-account key that can delete every database on the account. On plan gating, the documentation gates the API by account ORIGIN rather than by plan, and both managed products document a free plan value, but the reference does not say which plan gates the security add-ons it enumerates, and it does not state whether backups and teams are available on every tier. Check Upstash's pricing page before building a workflow that depends on the backup or team node families.

1

Confirm the account is a native Upstash account. If it was created through Vercel or Fly.io, the Developer API is not available to it and no key can be created.

2

In the Upstash console, open Account and then Management API, create a key with a distinct name, and copy it immediately.

3

In Mattering Automations, open Connectors, click Add Connector, choose Upstash, and create a credential with your account email and that key.

4

Click Test Connection. Mattering lists your Redis databases, which is the cheapest authenticated read on the API and takes no parameters at all, so it works on an account with nothing in it yet. A wrong key answers 401.

5

All 37 Upstash nodes appear in the canvas palette. Run Upstash: List Redis Databases and Upstash: List Vector Indexes first: those two feed the pickers on every other node.

Common uses for the Upstash MCP

Provision an environment, then record what it created

Upstash: Create Redis Database makes the database, and the response carries its id and endpoint host, which a Mattering database row can hold so the rest of your tooling knows where it is. Follow it with Upstash: Update Redis Budget to set a monthly spend ceiling, Upstash: Enable Redis TLS if the clients require it, and Upstash: Update Redis Read Regions to place replicas. One caution belongs with the first node: by default the create response and Upstash: Get Redis Database both carry the database's live connection credentials, so treat the output as secret material or set the credentials field to hide on the read.

Back up before anything risky, on the workflow rather than by memory

Upstash: Create Redis Backup is what makes a delete or a bulk rewrite survivable, so put it in front of both. Its response is worth designing around: it returns the string OK with no backup id, so the only way to find the backup just created is Upstash: List Redis Backups, and the state field there is what tells you it finished. Upstash: Enable Redis Daily Backup turns on the automatic schedule, and Upstash: Delete Redis Backup prunes old restore points, which is flagged destructive because a restore point is exactly what you miss when it is gone.

Vector index lifecycle without the console

Upstash: Create Vector Index, Upstash: Rename Vector Index, Upstash: Set Vector Index Plan and Upstash: Transfer Vector Index cover the whole management side of Upstash Vector, and Upstash: List Vector Indexes and Upstash: Get Vector Index read it back. Two things to know before you automate it. The similarity function and dimension count are fixed at creation and decide what embeddings the index can ever hold, so they must match whatever produces your vectors. And there is no Vector backup endpoint in the Developer API at all, so a deleted index has no restore point and the only recovery is re-embedding and re-upserting the source data.

Team and access hygiene as a scheduled job

Upstash: List Teams and Upstash: Get Team Members read who has access to what, with each member's role, and Upstash: Add Team Member and Upstash: Remove Team Member change it. A weekly sweep can write the whole picture into a Mattering database and open a task when someone appears where they should not be. Pair it with Upstash: List Audit Logs, which returns who did what, when, from which IP and through which client, and distinguishes a console action from an API-key one, so a change nobody remembers making has a trail.

Move a resource into a team when it stops being personal

Upstash: Move Redis Database To Team transfers a database's ownership and billing into a team while it keeps its id, endpoint host and credentials, so nothing connected to it breaks. Upstash: Transfer Vector Index does the same for an index. Read the asymmetry before you rely on it: Upstash states that transferring a Vector index to a personal account is not supported, so an index moved into a team cannot be moved back out through this API. Move deliberately, and move databases and indexes out of a team before deleting it, since deleting a team removes everyone's access through it.

Guard the bill rather than discovering it

Upstash: Update Redis Budget sets a monthly ceiling per database, Upstash: Change Redis Plan and Upstash: Set Vector Index Plan move resources between plans, and Upstash: Enable Redis Auto Upgrade lets Upstash move a database to a larger plan on its own when it outgrows the current one, rather than rejecting writes. Read that last one for what it is: a billing setting that raises the bill without asking, reversible with the disable node but not refundable. Upstash: Get Redis Database Stats reports request counts, throughput, latency percentiles, monthly bandwidth and month-to-date billing, so a scheduled read can open a task when the trend turns before the invoice does.

Example: A guarded restore that does not lose today's writes

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: an approval task moves to approved, carrying the database id and the backup to restore.

2

Upstash: Create Redis Backup runs FIRST, against the target database, because the restore is about to delete everything currently in it. The call returns the string OK with no id, so the next step reads it back.

3

Upstash: List Redis Backups finds the backup just taken and a condition waits for its state to report completed, since a restore run against a half-finished safety net is not a safety net.

4

Upstash: Restore Redis Backup restores the chosen backup. Upstash documents that all existing data in the target database is deleted before the restore begins, so this is the irreversible step and the reason for the two before it. The database id, endpoint host and credentials do not change, so clients stay connected and simply see different data.

5

Upstash: Get Redis Database reads the database back, with the credentials field set to hide so the run record does not carry live connection material for no reason.

6

The backup id, the restore time and the result land in a Mattering database, and a task is closed or opened depending on whether the restore reported success.

Upstash MCP questions, answered

What Upstash operations are supported?

37 nodes, which is the entire documented Upstash Developer API: 9 read and 28 act. Redis databases (list, get, stats, create, delete, rename, reset password, change plan, update budget, update read regions, enable and disable auto upgrade, enable and disable eviction, enable TLS, move to team), Redis backups (list, create, restore, delete, enable and disable daily backups), teams (list, get members, create, delete, add member, remove member), Vector indexes (list, get, create, delete, rename, reset tokens, set plan, transfer) and the account audit log. Not included, because they are different APIs with different credentials: the Redis REST data API, the Vector REST data API and QStash. The Developer API publishes no QStash and no Kafka endpoints at all.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively. Running them here rather than as a local tool also means they work on a schedule or a trigger with nobody present, chain with every other connector in one workflow, hold the management key in a shared workspace credential store rather than in an individual's config, and carry destructive flags you can gate on.

Upstash publishes its own MCP servers. Why use this connector?

Upstash does, and for some jobs they are the better answer. Upstash ships a Redis MCP server aimed at the data plane, whose tools run Redis commands against a database and search the Upstash documentation, and a broader Upstash MCP for account-level work including creating databases and reading QStash and Workflow logs. If you want an agent that runs Redis commands against your keys, use theirs: this connector never touches a database host and cannot do it. What this connector covers is the management API in full, including parts outside their server's scope, such as Vector index lifecycle, backups and restores, team membership, budgets and read regions, and the audit log. And it puts them somewhere different: as steps in scheduled and triggered workflows, chained with every other connector, on a credential the workspace holds rather than one developer's client config.

Can it read or write Redis keys, or query my vectors?

No, and that is a deliberate scope decision rather than a gap. Upstash runs four HTTP APIs and no two share a credential: the Developer API on api.upstash.com, the Redis REST API on each database's own host with that database's token, the Vector REST API on each index's own host with that index's token, and QStash with its own. This connector builds the Developer API only. Spanning would mean a credential form carrying five values for what a user experiences as one account, four of which are invalidated whenever a password is reset, and it would still be a half span, because the management API has no QStash surface to reach. So this connector manages Redis databases and Vector indexes without reading or writing what is inside them. The data APIs are ordinary bearer-token HTTP APIs, so a generic HTTP node reaches them today and each could become its own connector later.

Why can I not create a management API key?

Almost certainly because the account was not created directly with Upstash. Upstash documents the Developer API as available only to native Upstash accounts, and states that accounts created through third-party platforms such as Vercel or Fly.io are not supported. That is invisible from inside the product: the console works, the databases work, the data-plane tokens work, and there is simply no Management API page to create a key on and no error explaining it. No amount of retrying fixes it and there is no upgrade path inside this connector. The only fix is a native Upstash account.

Which nodes put secret material into workflow output?

Three reads, and they say so on the node. Upstash: Get Redis Database returns the database's live connection credentials by default, which the credentials parameter can set to hide. Upstash: List Vector Indexes and Upstash: Get Vector Index return each index's data-plane token and read-only token with no hide parameter available at all. Several writes are in the same position by their nature: Upstash: Create Redis Database returns the new database's credentials, and Upstash: Reset Redis Password returns the new password and REST token. Treat those runs' outputs as sensitive, set credentials to hide where the option exists, and prefer passing the value straight to whatever consumes it rather than leaving it in workflow state.

What do the two reset nodes actually break?

Every live client, and nothing else. Upstash: Reset Redis Password rotates the database's password and REST token, and Upstash: Reset Vector Index Tokens rotates an index's token and its read-only token together, so a read-only consumer breaks alongside the writer. No data is deleted and no key or vector is touched, but every application, worker, cron job and deployed environment variable holding a previous credential stops authenticating the moment the call returns, and the old value cannot be restored. Run them only when you are ready to redeploy everywhere in the same operation. The Redis one returns the new credentials in its response; the Vector one returns only the string OK, so read the new tokens back with Upstash: Get Vector Index.

What are Upstash's rate limits?

Upstash publishes no rate-limit documentation for the Developer API at all: there is no stated requests-per-second or per-minute ceiling, no quota figure, and no documented retry-after convention. So assume the API is rate limited, treat the ceiling as unknown, and do not build against a number, because this page will not invent one. The defensible guidance is behavioural: pickers resolve through a cached options read, so a config panel does not call the API on every keystroke, and a workflow should not poll the database lister in a tight loop. Separately, and unrelated to HTTP rate limiting, Upstash documents a default ceiling on how many API keys one user may hold, each needing a distinct name.

Which nodes are one-way?

Four are worth knowing, none of them flagged destructive because nothing is lost. Upstash: Enable Redis TLS has no disable counterpart in the reference, so it cannot be undone here. Upstash: Transfer Vector Index moves an index into a team, and Upstash states that transferring to a personal account is not supported, so it cannot be moved back out through this API. Upstash: Update Redis Read Regions replaces the whole set rather than adding to it, so a region left out of the list is removed along with its replica, which is easy to get wrong from a template that sends only the new one. And the plan and budget nodes are reversible in that the setting can be changed back, while the money spent in between cannot be. One naming point, because the vendor's own page titles disagree with the endpoint: the auto upgrade nodes are not autoscaling. They are a billing setting that moves a database to a larger plan when it outgrows the current one.

37 nodes waiting on the canvas

Put Upstash to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Upstash is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products