Datasource Workflow Blocks

Live Data, Every Run

Datasource blocks execute at run time — they query your external systems with the actual current data for each workflow run. Unlike static configuration, datasource blocks ensure that every proposal uses today's prices, every RFP response references the current project portfolio, and every quote reflects current inventory levels.

Each datasource block references a configured provider connection (set up once in Settings) and defines a query — which can be static or can include template variables populated from earlier workflow blocks.

Results from datasource blocks are structured JSON arrays or objects available to all downstream blocks — AI reasoning blocks, transform blocks, merge blocks, and proposal template fills.

The ERP pricing lookup block is specifically designed for the construction and manufacturing use case of querying a bill-of-materials or material list against your ERP's pricing engine. It accepts a list of material numbers and quantities, passes them to the ERP, and returns current prices, lead times, and availability — typically as a line-item enriched array.

Supported ERP Systems

• SAP S/4HANA / SAP ECC: SD condition records via OData; optionally invoke custom pricing BAPIs for complex pricing logic
• Oracle Fusion: Price list lookup via REST; supports customer-specific price lists
• Microsoft Dynamics 365 F&O: Trade agreements and price list entities via OData
• Custom ERP: Configure any REST endpoint that accepts a material list and returns pricing data

Input: Material List

The block accepts a material list array — typically output from an AI extraction block or a workbook line items array. Each item should include a material identifier (part number, material code, or ERP-internal ID) and an optional quantity for quantity-based pricing.

Output: Enriched Line Items

Returns the input array enriched with pricing fields: unit price, currency, discount tier, lead time days, and stock availability. The downstream merge block or proposal template can then use these enriched items directly.

// Input to ERP Pricing block
[
  { "material_no": "MAT-00142",
    "quantity": 24,
    "unit": "EA" },
  { "material_no": "MAT-00891",
    "quantity": 3,
    "unit": "SET" }
]

// Output from ERP Pricing block
[
  { "material_no": "MAT-00142",
    "quantity": 24,
    "unit_price": 142.50,
    "currency": "USD",
    "total_price": 3420.00,
    "lead_time_days": 5,
    "in_stock": true },
  { "material_no": "MAT-00891",
    "quantity": 3,
    "unit_price": 895.00,
    "currency": "USD",
    "total_price": 2685.00,
    "lead_time_days": 14,
    "in_stock": false }
]

Execute parameterized SQL queries against internal databases — PostgreSQL, MySQL, or SQL Server. The SQL query block uses a configured database connection (managed in RenderDraw Settings) and accepts a parameterized query where workflow data can be safely injected as query parameters (never string-concatenated — SQL injection prevention is enforced).

Configuration

• Connection: Named database connection from Settings > Providers
• Query: Parameterized SQL — use @param_name syntax for safe parameter injection
• Parameter mapping: Map workflow data fields to query parameters
• Result limit: Default 1000 rows; configurable up to 50,000
• Timeout: Query timeout threshold — fail gracefully rather than holding the workflow indefinitely

Security

SQL query blocks use read-only database users in all RenderDraw-managed connections. If you bring your own database credentials, we strongly recommend using a read-only user scoped to the minimum tables needed. Write operations are not supported in SQL query blocks — use a REST API call block or a dedicated write integration instead.

-- Example: Historical project lookup
SELECT
  project_name,
  project_type,
  total_value,
  margin_pct,
  completion_date
FROM projects
WHERE customer_id = @customer_id
  AND project_type = @project_type
  AND completion_date >= @cutoff_date
ORDER BY total_value DESC
LIMIT 10

Execute GraphQL queries and mutations against any GraphQL endpoint. Useful for Shopify product catalog, GitHub project data, internal GraphQL APIs, or any backend that exposes a GraphQL interface.

Configuration

• Endpoint URL: The GraphQL endpoint URL
• Query / Mutation: Full GraphQL query or mutation document — supports multi-line with introspection-based syntax validation in the block editor
• Variables: JSON variables object with workflow field injection via template syntax
• Authentication: Bearer token, API key header, or OAuth 2.0
• Response extraction: Select the path in the response data to return as the block output

Use Cases

• Query Shopify product catalog for current SKU pricing and availability
• Pull GitHub project issues and pull requests for software project proposals
• Query internal GraphQL API for project management data

query ProductPricing(
  $skus: [String!]!
) {
  products(skus: $skus) {
    sku
    title
    pricing {
      price
      currency
      availableQuantity
      leadTimeDays
    }
  }
}

// Variables
{
  "skus": "{{extraction.sku_list}}"
}