Connections
Connections store encrypted credentials for external services that your workflows interact with. When a node needs to access a database, SFTP server, or Redis instance, it uses a connection.
Supported Connection Types
| Type | Description | Used By |
|---|---|---|
| MySQL | MySQL database server | MySQL Query, Insert, Update, Delete nodes |
| PostgreSQL | PostgreSQL database server | PostgreSQL Query, Insert, Update, Delete nodes |
| Supabase | Supabase project | Supabase Query, Insert, Update, Delete nodes |
| SFTP | SFTP file server | SFTP Stream Read, Stream Write, List, Delete, Rename nodes |
| FTP | FTP file server | FTP file operations |
| Redis | Redis key-value store | Redis node |
| Google Sheets | Google Sheets API | Google Sheets Read, Append, Update, Clear nodes |
| Google Drive | Google Drive API | Google Drive List, Download, Upload, Delete nodes |
| DataStore | Built-in database | DataStore Query, Insert, Update, Delete nodes |
| Slack | Slack Bot Token | Slack Send Message, Update Message, Get Messages nodes |
How Connections Work
- Credentials are encrypted at rest — passwords and API keys are never stored in plain text
- Connections are shared across all workflows in your team
- Sensitive fields are masked in the UI after saving
- You can test a connection at any time to verify it works
Permissions
- Admins can create, edit, delete, and test connections
- Editors can view and use existing connections in workflows
- Viewers cannot access connections
See Managing Connections for step-by-step instructions.