These connector families are supported by the platform code and product documentation. Their presence does not mean they are configured for your account. Check the installed version, template, entitlement, network reachability and service authorisation before promising a workflow.
Databases#
The database connector supports MySQL, MariaDB and PostgreSQL. Its read operations can inspect tables and retrieve bounded query results. Write operations require separate enabling and a suitably authorised database account.
Use a dedicated database identity with the narrowest permissions, verified encrypted transport, row caps and query timeouts. A read-only workflow should also use read-only database permissions. Test against approved records before connecting production datasets.
Mailboxes#
The mailbox connector uses IMAP for supported mailbox access, with SMTP-related configuration for sending where enabled. It can support reading and searching as well as separately controlled actions that change or send messages.
Use the provider's supported account authorisation. An app password is not available on every provider or account policy. Keep sending, moving, deleting and unsubscribe actions outside a read-only test. The native mailbox connector is distinct from the separate DigLab Inbox platform integration.
Files#
File connectors support SFTP, FTPS and FTP routes. Prefer an appropriately verified encrypted protocol and a dedicated account restricted to the intended directory. Define the allowed path boundary before enabling uploads, edits or deletion.
Test a harmless listing or read first. Do not connect an unrestricted server filesystem or expose configuration and authentication directories as general AI tools. File access and operating-system administration are different capabilities.
WordPress and commerce#
Supported WordPress and WooCommerce configurations expose selected site or store operations through their official interfaces. Verify the exact site, account role and read/write scope. A site being reachable does not prove the connection can publish or change store data.
Start with an approved test item. Draft creation, publication, customer-data access and order changes require distinct acceptance. Never use another brand's site credential to make a connection appear complete.
Other APIs#
Use the supported API import or visual tool editor for services with an official REST interface. A remote MCP-only product requires a separately supported connection method; pasting an MCP URL into a REST tool is not a verified integration.