Documentation: Credentials
Flowy credentials
Flowy treats credentials as a dedicated object type, cleanly separating sensitive connection data from your process logic. This makes credentials easier to manage, rotate, and secure — independent of the processes that use them.
Credential values can optionally be encrypted for an additional layer of protection. By design, Flowy does not version-control credentials, preventing previous values from being recoverable after an update.
Note
While Flowy takes robust measures to protect credentials, it's important to be aware of certain security considerations. During the export to a module, specific properties and their values are intentionally omitted for security reasons. This is a deliberate design choice aimed at maintaining the security of the system and the confidentiality of the data. It helps prevent accidental leaks of sensitive information during the export process.
Flowy supports the following credential types:
Anthropic
Used to access Anthropic's Claude API for large language model capabilities.
AWS
Used to connect to Amazon Web Services. Supports access to S3, SES, and other AWS services.
DeepSeek
Used to access the DeepSeek API for large language model capabilities.
Flowy
Used for authentication against other Flowy instances.
FTP
Used to connect to FTP and FTPS servers for file transfer operations. FTPS (FTP over SSL/TLS) can be enabled on the FTP step configuration.
Git
Used to authenticate against Git repositories. Supports both token-based and SSH key-based authentication.
IMAP
Used to receive emails via the IMAP protocol.
JDBC
The following formats should be used for URL entry:
PostgreSQL
jdbc:postgresql://<host>:<port>/<databaseName>
MySql
jdbc:mysql://<host>:<port>/<databaseName>
Oracle
jdbc:oracle:thin:@<host>:<port>:<databaseName>
Sql Server
jdbc:sqlserver://<host>;databaseName=<databaseName>
The console and browse functionality are only available when the "Allow usage of Query Console" option is enabled.
Jira
Used to connect to Jira for issue tracking and project management integration.
JMS
Used to connect to Java Message Service (JMS) brokers such as ActiveMQ.
JWT
Used to create and manage JSON Web Tokens for authentication and authorization.
Kafka
Used to connect to Apache Kafka message brokers for producing and consuming messages.
LDAP
Used to connect to LDAP or Active Directory servers for directory lookups and authentication.
MCP HTTP
Used to connect to Model Context Protocol servers via HTTP.
MCP SSE
Used to connect to Model Context Protocol servers via Server-Sent Events (SSE).
MCP Stdio
Used to connect to Model Context Protocol servers via standard input/output.
MongoDB
Used to connect to MongoDB databases.
Please enter the URL in the following format:
mongodb://<username>:<password>@host1:port1[,...hostN[:portN]]/<databaseName>?[options]
When attempting to connect to DocumentDB the following steps must be executed upfront:
# download certificates, these depend on the locaton of your server
# eu-west-1 is used throughout this example
wget https://truststore.pki.rds.amazonaws.com/eu-west-1/eu-west-1-bundle.pem
# convert the certificate
openssl x509 -outform der -in eu-west-1-bundle.pem -out eu-west-1-bundle.der
# import the certificate to the default keystore
keytool -import -alias eu-west-1-bundle -keystore $JAVA_HOME/lib/security/cacerts -file eu-west-1-bundle.der
MQTT
Used to connect to MQTT brokers for lightweight publish/subscribe messaging. Supports optional SSL/TLS for secure connections.
MS Graph API
Used to access the Microsoft Graph API for integration with Microsoft 365 services such as Outlook, Teams, and SharePoint.
OpenAI
Used to access the OpenAI API for large language model capabilities.
Paymentsense Connect E
Used to connect to the Paymentsense Connect E payment gateway.
Paymentsense PAC
Used to connect to the Paymentsense PAC payment service.
Plugin
Used to store configuration for Flowy plugins. The credential values are a flexible key-value map, where the required fields depend on the specific plugin being configured.
RabbitMQ
Used to connect to RabbitMQ message brokers. Supports optional SSL/TLS for secure connections.
Rest
Used for generic REST API connections. The credential values are a flexible key-value map, allowing any custom fields to be stored. For common authentication patterns, consider using the dedicated REST Basic or REST Bearer credential types instead.
REST Basic
Used for REST API connections with HTTP Basic authentication.
REST Bearer
Used for REST API connections with Bearer token authentication.
Script
Used to store parameters for custom script execution. The credential values are a flexible key-value map, where the fields depend on what the script requires.
Security
Used to store encryption keys and passphrases for securing data within processes.
SFTP
Used to connect to SFTP servers for secure file transfer. Supports both password and SSH key-based authentication.
Slack
Used to send messages to Slack channels via the Slack API.
SMTP
Used to send emails via the SMTP protocol.
SSH
Used to establish SSH connections with password-based authentication.
SSH Key
Used to establish SSH connections with key-based authentication.
Stripe Connect
Used to connect to the Stripe payment platform for payment processing.
Twilio
Used to send SMS and voice messages via the Twilio API.
Used to send messages via the WhatsApp Business API.