Deldai is designed to work alongside cloud platforms, data systems, AI models, infrastructure, developer tools, and workflow automation. Availability depends on the integration path and configuration.
Workflow automation
Build workflows with n8n and Make
Connect through HTTP requests using a Deldai integration API key. These are API-based setup paths, not one-click native connectors.
n8n
HTTP API
Use an HTTP Request node to check connectivity or trigger an AI visibility run from a workflow.
Setup outline
Add an HTTP Request node.
Use the Deldai API endpoint and select GET or POST as required.
Send the API key in the Authorization header as a Bearer token.
Map the JSON response into the next workflow step.
Make
HTTP API
Use an HTTP module to call Deldai from a scenario and pass the response to downstream modules.
Setup outline
Add an HTTP request module to your scenario.
Configure the Deldai endpoint and request method.
Set Authorization to Bearer followed by your integration API key.
Map the JSON response to subsequent modules.
Available API endpoints
The integration API currently exposes connectivity checks and AI visibility run execution. Requests use Bearer authentication and require the appropriate key scope.
GET /api/integrations/v1/health
Requires the runs.read scope. Returns connection status and the key's granted scopes.
POST /api/integrations/v1/ai-visibility-runs
Requires the runs.execute scope. Accepts a JSON body containing a querySetId and optional provider, mode, and purpose.
Keep credentials secure
Store API keys in your automation platform's supported credential store. Do not place secrets in client-side code, public workflow exports, or logs. Use separate keys with only the scopes each workflow needs, and revoke keys that are no longer required.
Technology ecosystem
Designed for the enterprise stack
Explore the platforms and technologies relevant to Deldai's architecture. Listing a technology here does not imply that a dedicated native connector is available.