Create your first endpoint
Sign up, define a URL, and configure auth and validation in a few clicks.
Databases
Use connected datastores as your endpoint database layer for API, webhook, and automation workflows.
What you can do with databases
- Use Google Sheets, PostgreSQL, MySQL, Redis, MongoDB, and more as workflow data sources
- Read and write records with datastore actions instead of custom controller code
- Power forms, webhook processing, and APIs from one database-backed endpoint
- Keep auth, validation, and response contracts around every database workflow
422
200
404
Database use case library
Explore ways to use connected datastores as the database behind no-code API and webhook workflows.
Use Airtable as a database
Use Airtable as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use DynamoDB as a database
Use DynamoDB as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use Google Sheets as a database
Use Google Sheets as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use MariaDB as a database
Use MariaDB as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use Memcached as a database
Use Memcached as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use MongoDB as a database
Use MongoDB as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use MySQL as a database
Use MySQL as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use Notion as a database
Use Notion as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use PostgreSQL as a database
Use PostgreSQL as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use Redis as a database
Use Redis as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use SQL Server as a database
Use SQL Server as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use SQLite as a database
Use SQLite as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use Supabase as a database
Use Supabase as a database for Streamnode APIs, webhooks, and endpoint workflows without writing backend boilerplate.
Use existing datastores as your endpoint database
Plug datastore connections into endpoint workflows and keep request validation, auth, and response contracts in one place.
Database-backed endpoint workflows
Connect once, then reuse across API and webhook routes.
- Use connected datastores like Google Sheets, PostgreSQL, MySQL, Redis, MongoDB, Airtable, and more.
- Read, create, update, and delete records directly from endpoint actions.
- Branch response outcomes for success, validation errors, and missing resources.
POST streamnode.app/customer-upsert
01
Validate
Check auth and input shape.
02
Query datastore
Read or mutate database records.
03
Respond
Return stable HTTP payloads.
Get started in minutes
Everything you need to go from zero to production-ready endpoints.
Follow the quickstart
Use the docs to build and test a full endpoint workflow step by step.
Pick a plan when you are ready
Start free, then upgrade for higher limits, advanced features, and team workflows.
Build this workflow in Streamnode
Start with a URL, add validation and actions, then ship the response your clients need.