INTFLOW: Integration Flow
A configurable integration workflow that receives external webhooks and executes a pipeline of steps to fetch, transform, and route data between external systems and DemandFlow.
Default definition. This article describes the default
INTFLOW definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches INTFLOW.Entity properties
| Property | Value |
|---|---|
| Entity code | INTFLOW |
| Display name | Integration Flow |
| Plural | Integration Flows |
| Level | 11200 |
Use cases
Top-level entity for the integration engine. Two panels: General has config (basics, trigger, connections, notifications, execution status) in a two-column layout. Steps panel has the pipeline via intsteparray row type at full width.
Fields
Basics
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Flow name. |
description | text (multi-line) | Description. | |
active | boolean | Active. |
Trigger
| Field | Type | Required | Notes |
|---|---|---|---|
triggerType | enum | Yes | Valid ids: webhook (Webhook), scheduled (Scheduled), manual (Manual), email (Inbound email). |
webhookPath | text | URL slug for this flow. Must be unique within your tenant. The full URL is shown below. | |
webhookFullUrl | text | POST to this URL with your trigger payload as JSON. The tenant id is included in the path so paths only need to be unique within your own subscription. | |
authMode | enum | Valid ids: none (No authentication), header (Custom header check), bearer (Bearer token), apiKey (API key). | |
authHeaderName | text | Name of the header to check, e.g. 'app' | |
authHeaderValue | text | Expected value of the auth header, e.g. 'demandflow' | |
schedule | enum | Valid ids: 1min (Every minute), 5min (Every 5 minutes), 15min (Every 15 minutes), 1hr (Every hour), 12hr (Every 12 hours), daily (Daily), weekly (Weekly), monthly (Monthly). | |
inboundEmailAddress | text | Forward or send emails to this address. Each message will trigger this flow with the parsed email as the payload. |
Connections
| Field | Type | Required | Notes |
|---|---|---|---|
integration | enum | The primary external system connection for this flow Valid ids: dynamics (Dynamics 365), quickbooks (QuickBooks). | |
integration2 | enum | Optional secondary connection for this flow Valid ids: dynamics (Dynamics 365), quickbooks (QuickBooks). |
Notifications
| Field | Type | Required | Notes |
|---|---|---|---|
notifyEmails | text (multi-line) | Comma-separated email addresses for notifications |
Logging
| Field | Type | Required | Notes |
|---|---|---|---|
logSourceId | reference → LOGSOURCE | When set, this flow's events (start, log steps, errors, completion) are routed into the DemandFlow SIEM as LOG records under this source. |
Last execution
| Field | Type | Required | Notes |
|---|---|---|---|
lastRunAt | datetime | Last run. | |
lastRunStatus | enum | Valid ids: success (Success), error (Error), skipped (Skipped). | |
lastRunLog | text (multi-line) | Execution log. |
Relationships
- Lookups:
logSourceIdpoints at aLOGSOURCErecord.
Creating a Integration Flow via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "INTFLOW",
"level": 11200,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"triggerType": "webhook",
"description": "...",
"active": true
}Listing Integration Flows
# All records in your tenant
GET /v1/entities/INTFLOW/SUB:<your-sub-id>