Every block available in the RenderDraw visual workflow engine — organized by category, with inputs, outputs, and common use cases for each.
| Block Name | Category | Primary Output | Common Use |
|---|---|---|---|
| Email Trigger | Trigger | Parsed email object | Ingest RFPs, RFIs, purchase orders |
| File Upload Trigger | Trigger | File metadata + storage URL | Receive CAD files, PDFs, drawings |
| Webhook Trigger | Trigger | Raw payload JSON | Procore events, custom system events |
| Schedule Trigger | Trigger | Timestamp + context | Daily reports, weekly pricing refresh |
| Salesforce Event Trigger | Trigger | SF record change data | Opportunity updates, new leads |
| SharePoint Trigger | Trigger | File metadata + download URL | New drawings, spec updates |
| Manual Trigger | Trigger | User-supplied input fields | On-demand runs, testing |
| AI Text Reasoning | AI | Structured JSON or freetext | Requirement extraction, draft generation |
| AI Document Analysis | AI | Extracted fields JSON | RFP scope extraction, contract review |
| AI Vision Analysis | AI | Detected objects JSON | Takeoff from drawings, BOM from photos |
| AI Structured Extraction | AI | Typed schema JSON | Pull quantities, dates, specs from docs |
| AI Summarization | AI | Summary text | Meeting notes, RFI history summary |
| AI Draft Generation | AI | Draft document text | RFP response narrative, cover letters |
| Knowledgebase Query | AI | Matched passages JSON | Historical pricing, product specs lookup |
| CRM Query | Datasource | Records array | Customer history, contact lookup |
| ERP Pricing Lookup | Datasource | Price list JSON | SAP/Dynamics material costs |
| Spreadsheet Read | Datasource | Table JSON | Rate sheets, bid history Excel |
| SQL Query | Datasource | Rows JSON | Internal database lookups |
| REST API Call | Datasource | Response JSON | Any external REST endpoint |
| GraphQL Query | Datasource | Query result JSON | Shopify, GitHub, custom APIs |
| Map Fields | Transform | Remapped object | Normalize field names across sources |
| Filter Array | Transform | Filtered array | Scope down line items by criteria |
| Merge Objects | Transform | Combined object | Combine CRM + ERP data |
| Compute Fields | Transform | Enriched object | Totals, markups, unit conversions |
| Branch / Decision | Decision | Route selection | High-value vs. standard quote paths |
| Wait / Delay | Decision | Timestamp continuation | SLA timers, scheduled follow-up |
| Loop Over Array | Decision | Per-item results | Process each line item, each drawing |
| Human Approve/Reject Gate | Human Gate | Approval decision + notes | Pre-send review for proposals |
| Structured Review Form | Human Gate | Form field responses | Reviewer inputs corrections to AI draft |
| Multi-Approver Gate | Human Gate | Consensus decision | Large contracts requiring 2+ approvals |
| CAD Conversion | CAD | GLB/GLTF URL | STEP/SolidWorks/Revit to 3D web |
| Conversion Status Poll | CAD | Status + progress % | Wait for long conversion jobs |
| PDF Generation | Proposal | PDF file URL | Render proposal from template |
| Conga CPQ Submit | Proposal | Conga quote record | Push to Conga for pricing/approval |
| DocuSign Envelope | Proposal | Envelope ID + signing URL | E-signature for contracts |
| Start Configuration | Configuration | Session ID + fields | Open native, Logik, Conga, Infor, or Salesforce configuration |
| Set Configuration Value | Configuration | Updated validation state | Apply selections from RFP requirements or estimator edits |
| Get Configuration BOM | Configuration | BOM line items | Turn selections into sales, manufacturing, or custom BOM rows |
| Price | Pricing | Price result | Dispatch configured products or pricing rollups to the CPQ adapter |
| Create Quote | Quote | Quote handle | Create a provider-backed quote without changing downstream wiring |
| Push Line Items | Quote | Push result | Attach approved line items to the quote of record |
| Email Delivery | Notification | Send confirmation | Proposal delivery, reviewer notifications |
| Slack Notification | Notification | Message confirmation | Gate alerts, completion notifications |
| Teams Notification | Notification | Message confirmation | Enterprise Teams integration |
| Salesforce Update | Proposal | Updated record | Update opportunity stage, attach proposal |
Trigger blocks are the entry point of every workflow. They define what event starts a run and what initial data is made available to downstream blocks. A single workflow can be started by multiple different trigger types.
Description: Monitors a dedicated inbox (or a shared mailbox via Microsoft 365 / Google Workspace delegation). Fires a new workflow run for each inbound email matching configured filter rules (sender domain, subject keyword, attachment type).
Inputs: Mailbox configuration, filter rules, attachment handling (inline vs. extracted).
Outputs: Parsed email object — from, to, cc, subject, body text, attachments array with storage URLs.
Common uses: Ingest RFPs and bid invitations, receive customer drawing submittals, capture purchase order emails, start RFI response flows from subcontractor emails.
Description: Fires when a file is uploaded to a configured storage location — RenderDraw's own upload portal, an S3 bucket, Azure Blob container, SharePoint library, or Google Drive folder.
Inputs: Storage provider, folder/bucket path, file type filter (PDF, DWG, STEP, XLSX, etc.).
Outputs: File metadata object — filename, size, mime type, upload timestamp, download URL for downstream blocks.
Common uses: Receive CAD drawings for takeoff, ingest specifications for AI analysis, process new rate sheets, start conversion workflows on STEP upload.
Description: Exposes a unique HTTPS endpoint per workflow. Any system that can make an HTTP POST can trigger a workflow run — Procore, Autodesk Construction Cloud, custom ERP events, or any build/deploy system.
Inputs: Optional secret for HMAC signature verification, payload schema for input validation.
Outputs: Raw JSON payload as parsed workflow data, plus request metadata (timestamp, source IP).
Common uses: Procore submittal events, Salesforce flow callouts, custom system integration, CI/CD triggered document generation.
Description: Runs a workflow on a repeating schedule using standard cron expressions or simple intervals (daily, weekly, monthly). Supports timezone-aware scheduling so workflows run at the right local time for your team.
Inputs: Cron expression or interval selection, timezone, optional context payload injected at each run.
Outputs: Run timestamp, schedule metadata, any injected context fields.
Common uses: Daily pricing refresh from ERP, weekly project status reports, monthly bid pipeline exports, quarterly knowledgebase update pulls.
Description: Subscribes to Salesforce Platform Events or Change Data Capture streams. Fires a workflow run whenever an Opportunity, Account, Contact, or custom object changes in Salesforce — no polling, pure event-driven.
Inputs: Salesforce OAuth connection, object type, event type (created / updated / deleted), field filter.
Outputs: Changed record fields, change type, actor user, timestamp.
Common uses: Start RFP workflow when Opportunity stage changes to "Bid Required", trigger quote rebuild when pricing tier changes, notify team when new Account is created.
Description: Watches a SharePoint document library for new or modified files. Fires on file creation, file update, or folder changes. Uses Microsoft Graph webhooks for near-real-time delivery.
Inputs: Microsoft 365 OAuth connection, site URL, library path, file type filter, event type.
Outputs: File metadata, SharePoint item ID, download URL, modifier user, change timestamp.
Common uses: Process new specification documents uploaded by architects, react to updated drawings in project SharePoint, ingest revised RFP documents.
AI blocks invoke large language models for reasoning, extraction, analysis, and generation. Each block is independently configurable — different model, different system prompt, different temperature — so you can mix fast cheap models for classification with powerful models for complex reasoning in the same workflow.
Description: General-purpose LLM invocation. Provide a system prompt, inject workflow data as context, and receive freetext or structured JSON output. Supports Claude Sonnet, Claude Opus, Claude Haiku, GPT, Gemini Pro, and custom endpoints.
Common uses: Classify document type, determine bid/no-bid recommendation, generate executive summary, answer a question from knowledgebase context.
Description: Analyzes multi-page PDF or Word documents. Handles documents up to hundreds of pages by chunking and summarizing. Returns structured extraction of key fields defined in your schema.
Common uses: Extract scope of work, deadlines, submission requirements, and evaluation criteria from RFP documents. Parse contract terms. Identify compliance requirements from specification sections.
Description: Analyzes images and 2D drawings using vision-capable models. Identify objects, count elements, read labels, and extract spatial relationships from floor plans, construction drawings, and site photos.
Common uses: Count fixtures from MEP drawings, identify material types from site photos, read labels on P&ID diagrams, detect changes between drawing revisions.
Description: Extract specific fields from unstructured text using a defined output schema. The block validates the model output against your schema and retries with corrective prompting if the structure is malformed.
Common uses: Pull material quantities and units from takeoff notes, extract payment terms from contracts, parse delivery dates from purchase orders, read line items from bid tabs.
Description: Condense long documents, email threads, meeting transcripts, or arrays of records into concise summaries at a configured length and detail level.
Common uses: Summarize RFI thread history for a new reviewer, condense project meeting notes, generate a one-paragraph project overview from a full specification.
Description: Generate long-form draft content with injected context from earlier blocks — pricing data, extracted requirements, company boilerplate from knowledgebase. Outputs editable draft text ready for human review gate.
Common uses: Draft RFP response narrative sections, write cover letter for proposal, generate executive summary for bid package, draft preliminary RFI response.
Description: Semantic search against a configured RenderDraw knowledgebase — past projects, product specs, pricing history, company standards, technical documentation. Returns ranked passages with source attribution.
Common uses: Find relevant past project data for RFP response, lookup product specification for a given part number, retrieve company boilerplate for proposal sections, check precedent pricing for material category.
Learn about Knowledgebases →Datasource blocks connect to live external systems and return structured data that can be used in downstream blocks. Each block authenticates via a configured provider connection — set up once, reuse across all your workflows.
Full Datasource Block Reference →Query Salesforce, HubSpot, or Dynamics CRM for accounts, contacts, opportunities, and custom objects. Filter, sort, and limit results. Returns records array.
Call SAP, Oracle, Dynamics ERP, or custom pricing APIs. Pass a list of material numbers and receive current prices, lead times, and availability.
Read Excel or Google Sheets data as a structured table. Select sheet, row range, and column mapping. Handles large sheets via streaming.
Execute parameterized queries against PostgreSQL, MySQL, or SQL Server. Pass workflow data as query parameters. Returns rows as JSON array.
Make HTTP GET/POST/PUT requests to any external REST API. Configure headers, body, authentication, and response field mapping.
Execute GraphQL queries against Shopify, GitHub, or any custom GraphQL endpoint. Define your query and variable mapping in the block configuration.
Transform blocks reshape data between steps. They have no external side effects — pure data manipulation that is deterministic, fast, and fully logged.
Rename, extract, and restructure fields from an input object. Use dot-notation paths to access nested fields. Create a new output shape without modifying the source. Common use: Normalize field names between Salesforce opportunity fields and your proposal template schema.
Filter an array of objects by field value, type, or expression. Remove nulls, filter by status, select items above a threshold. Common use: Select only line items above $5,000 for executive summary section of proposal.
Deep-merge two or more objects from different blocks into a single combined object. Configure merge strategy (last-write-wins, first-write-wins, array concat). Common use: Combine CRM customer data with ERP pricing data for the proposal context.
Add computed fields to an object using simple formula expressions — multiplication, addition, string interpolation, conditionals. Common use: Calculate total price with markup, convert square feet to square meters, format date fields for a proposal template.
Evaluate a condition on workflow data and route execution to one of multiple downstream paths. Conditions use the same expression language as filter blocks — field comparisons, regex match, array contains. Configure as binary (if/else) or multi-path (switch/case).
Common uses: Route high-value bids to senior estimator gate; route known customers to fast-track path; branch by project type for different proposal templates.
Pause workflow execution until a specified time or duration elapses. The workflow run remains durable during the wait — no resources consumed, no polling. Supports absolute timestamps and relative durations.
Common uses: Send follow-up email 3 days after proposal delivery. Wait until 9 AM in the recipient's timezone. Schedule re-pricing after 30 days if bid not won.
Iterate over an array of items, executing a sub-workflow for each one. Results are collected back into an array. Supports parallel execution (all items at once) or sequential execution (one at a time).
Common uses: Process each drawing file in an uploaded set; query ERP pricing for each line item in a BOM; run AI analysis on each section of a multi-part RFP.
Human gate blocks are the mechanism for keeping humans in control of automation. They pause the workflow, route to the right reviewer, and resume only after a human decision is recorded.
Full Human Gates Reference →Pauses the workflow and sends a notification (email, Slack, Teams) to the configured reviewer. The reviewer sees a summary of the workflow data and clicks Approve or Reject. Rejection routes to a configured fallback path or ends the run.
Outputs: Decision (approved/rejected), reviewer identity, decision timestamp, optional rejection reason text.
Presents the reviewer with a configurable form — text fields, number inputs, dropdowns, checkboxes — pre-populated with AI-generated draft values. The reviewer can correct, confirm, or override each field. Outputs the reviewed and corrected data object.
Common uses: Estimator reviews and corrects AI-extracted quantities before pricing. Engineer reviews AI-drafted RFI response before submission.
Requires approval from multiple named reviewers — any N of M (configurable quorum) or unanimous. Each reviewer sees the full workflow context and submits their independent decision. Workflow resumes when quorum is reached or fails if too many reject.
Common uses: Large contracts requiring VP + Director sign-off. Proposals above a value threshold requiring two estimators. Change orders requiring owner + GC approval.
Only presents the human gate if a workflow condition is true. Below-threshold or low-risk runs bypass the gate automatically; above-threshold runs are held for review. Combines the decision logic of a branch block with a human gate for dynamic routing.
Common uses: Require human review for quotes above $250,000; auto-approve quotes for known preferred customers; require review when AI confidence score is below threshold.
CAD conversion blocks trigger HOOPS Exchange file conversion and feed the resulting 3D web assets into your workflow — for AI vision analysis, workbook population, or 3D viewer delivery.
Full CAD Blocks Reference →Submit a CAD file (STEP, IGES, SolidWorks, Revit, Inventor, CATIA, and 30+ formats) for conversion to GLB/GLTF 3D web format via HOOPS Exchange. Returns a job ID for status polling.
Check the status of a conversion job. Automatically retries on a configured interval until the job completes (success or failure). Returns the output GLB URL on success.
Proposal blocks are the final stage of most workflows — they take the structured data assembled and reviewed upstream and convert it into deliverables that leave the system.
Full Proposal Blocks Reference →Render a proposal PDF from a configured template. Map workflow fields to template placeholders. Handle conditional sections, tables, and embedded 3D viewer links.
Push quote data to Conga CPQ for pricing finalization. Returns the Conga quote record ID and approval status for use in downstream blocks.
Create a DocuSign envelope from a generated PDF. Configure signer roles and routing order. Returns the signing URL and envelope ID.
Configurator blocks open durable product-configuration sessions, apply feature values, validate rules, derive BOMs, and finalize the configuration before pricing. RenderDraw exposes the same lifecycle for its native configurator and provider-specific CPQ engines.
Full Configurator Blocks Reference →Open a native, Logik, Conga, Infor, or Salesforce session and emit the session handle that downstream blocks use.
Apply AI- or human-selected feature values, re-run the rules engine, and route invalid selections to a correction path.
Derive sales, manufacturing, or custom BOM rows, then emit the terminal configuration state for pricing and quote creation.
Pricing and quote blocks provide the provider-agnostic CPQ pipeline: price a configuration, create a quote, push line items, and read price-book items through one adapter contract.
Full Pricing & Quote Reference →Send a configuration result or pricing bucket rollup to the selected CPQ connection and return a structured price result.
Create a provider-backed quote and emit a unified quote handle so downstream workflow wiring stays portable.
Attach approved line items to the quote of record after pricing, margin review, and human approval gates complete.
Send transactional or bulk email via MailerSend, Microsoft 365, or Google Workspace SMTP. Attach generated PDFs, 3D viewer links, or file downloads. Full template support with workflow data injection.
Post structured messages to Slack channels or direct messages. Include rich formatting — data tables, action buttons, file links. Use for human gate alerts, completion notifications, and error escalation.
Post adaptive card messages to Microsoft Teams channels or individual users. Supports approval action buttons directly within the Teams notification for human gate review without leaving Teams.
Start from a template or build from scratch. Every block is configurable, every connection is typed, and every run is fully auditable.