› CIS-DF Hub › Part 8 › IntegrationHub & Flow Designer
⬡ Part 8 · Topic 2

IntegrationHub & Flow Designer

Flow Designer provides a no-code/low-code automation canvas. IntegrationHub adds pre-built "spokes" that connect to external systems. Together they enable data-driven automations without writing custom API code.

📋 4 sections ⏱ ~16 min read 🎯 ~7% exam weight 🏷 IntegrationHub · Flow Designer
Section 1

Flow Designer Overview

Flow Designer is ServiceNow's visual automation tool where you build workflows using a drag-and-drop canvas. It replaces older scripted automation approaches with a structured, no-code interface. Each flow is a sequence of:

  • Trigger — what starts the flow (record created, scheduled, inbound webhook, manual)
  • Actions — what the flow does (look up record, update field, call REST API, send email)
  • Logic — conditions (If/Else), loops (For Each), error handling
🧩
Analogy — Recipe Card for IT Automation Flow Designer is like a recipe card. The trigger is "when to start cooking" (e.g., when a CI is discovered with no owner). The actions are the steps (look up the CI, find the responsible team, assign ownership, send confirmation email). Anyone can read the recipe card without needing to be a chef (programmer).
Section 2

IntegrationHub Spokes

IntegrationHub extends Flow Designer by providing pre-built Spokes — bundles of Actions for specific external systems. Instead of writing code to call Jira's API, you use the Jira Spoke which has actions like "Create Issue," "Update Issue," "Get Issue Status."

Spokes are installed from the ServiceNow Store and require an IntegrationHub license. Commonly available spokes include:

  • Jira, GitHub, GitLab (development tools)
  • AWS, Azure, GCP (cloud infrastructure)
  • Slack, Microsoft Teams (communication)
  • Active Directory, Okta (identity)
  • Generic REST, SOAP (for custom integrations)
Section 3

Flow Designer vs. Business Rules vs. Workflows

ToolWhen to UseCode Required?
Flow DesignerModern automations, cross-system integrations, record lifecycle managementNo (low-code)
Business RulesServer-side logic that must run during record insert/update/delete. Fast synchronous execution.Yes (JavaScript)
Workflow (Legacy)Legacy approval processes, SLA management. Being replaced by Flow Designer.Partially
Scheduled JobsRun scripts on a time schedule (daily cleanup, batch operations)Yes (JavaScript)
⚠
Exam Trap — Flow Designer Is Asynchronous by Default Flow Designer flows run asynchronously by default — meaning they're queued and executed separately from the transaction that triggered them. If you need an action to complete before the user's save operation finishes (blocking behavior), use a Business Rule, not a Flow. Async execution is more scalable but means the user won't see immediate results from the flow.
Section 4

CMDB Automation with Flow Designer

Flow Designer is well-suited for CMDB governance automation:

  • Auto-assign CI ownership — when a new CI is discovered, trigger a flow that looks up the CI's location, finds the responsible group for that data center, and sets managed_by automatically
  • Stale CI notification — scheduled flow that queries CIs with last_discovered older than 60 days and creates tasks for the relevant owners to review
  • Lifecycle transitions — when a Change Request is closed, trigger a flow to update the CI's lifecycle_stage to "Operate" and operational_status to "Operational"
  • Cross-system sync — when a CI is retired in ServiceNow, use an IntegrationHub spoke to also update the corresponding record in the CMDB of an external ITSM tool
Exam Quick Reference

Common Exam Traps — IntegrationHub & Flow Designer

  • Flow Designer = no-code visual automation (Trigger → Actions → Logic)
  • IntegrationHub Spokes = pre-built actions for external systems; requires license
  • Flow Designer is async by default — not for blocking operations (use Business Rules)
  • Business Rules = synchronous, server-side JS; Flow Designer = async, no-code
  • Legacy Workflows are being replaced by Flow Designer — for new builds, use Flow Designer
Exam Checkpoint

Practice Questions

4 questions · Select an answer to see the explanation immediately.

IntegrationHub & Flow Designer Quiz 1 / 4

A business analyst needs to create an automated process that: when an Incident is resolved (trigger), sends a Slack notification to the assignment group channel (action), and creates a follow-up task (action). No coding experience. Which tool should be used?

💡 Explanation

B is correct. Flow Designer is specifically designed for no-code/low-code automation with a visual interface: define a Trigger (Incident state changes to Resolved), add Actions (Slack notification via IntegrationHub Slack Spoke, Create Task record). IntegrationHub Spokes provide pre-built Actions for external systems like Slack, Jira, and ServiceNow itself. No coding required. Business Rules (A) require JavaScript. Client Scripts (C) are browser-side and only run during form interactions, not suitable for reliable server-side automation. REST API (D) requires coding and infrastructure, not a no-code tool.

A field validation that must block an Incident from saving when impact=1 AND urgency=3 needs to be implemented. Should this use a Business Rule or Flow Designer?

💡 Explanation

B is correct. Business Rules with Before timing execute synchronously before the record is committed to the database. This allows calling current.setAbortAction(true) to prevent the save. Flow Designer is asynchronous by default — it fires after the record is saved, so it cannot block the save operation. For blocking operations (field validation that prevents saves), Business Rule Before timing is the only correct choice. UI Policies (D) block form submissions client-side but are bypassed by API calls. For server-enforced save blocking, Before Business Rule is required.

An IntegrationHub Spoke for Jira requires a separate license. A team builds a Flow Designer flow that calls the Jira REST API directly using the HTTP Action instead. What is the implication?

💡 Explanation

B is correct. IntegrationHub Spokes are pre-built, tested collections of Actions for specific external systems — they provide "Create Jira Issue," "Update Jira Status," etc. as ready-to-use Actions without needing to configure API endpoints, authentication, or request/response mapping. Using the generic HTTP Action instead is functionally equivalent but requires manually setting up everything the Spoke would handle automatically. The tradeoff: Spoke requires a license but saves significant implementation and maintenance effort; HTTP Action approach is free but requires more technical configuration work. Both are valid approaches depending on licensing and technical resources.

An organization is updating existing automation that currently uses Legacy Workflows. New automation requirements are being added. Should they extend the Legacy Workflow or build new automation?

💡 Explanation

B is correct. ServiceNow's official guidance is that Legacy Workflows are being replaced by Flow Designer. For new automation requirements, Flow Designer should always be used. Legacy Workflows are still supported for backward compatibility but receive no new investment. Adding new automation to a Legacy Workflow increases technical debt and extends the migration surface. The recommended approach: build all new automation in Flow Designer, and plan to migrate existing Legacy Workflows to Flow Designer incrementally. Flow Designer supports all the capabilities needed for complex multi-step automation (D is incorrect).

Score: 0 / 4
Archiving, Purging & Retention →