EdgazeDocsEdgaze Docs
BuilderBilling & RunsAPI ReferenceMCPLegal & TrustChangelog
DocumentationAPI Reference
Home
Core
Ask for InputResultMerge
AI
Generate TextGenerate Image
Logic & utilities
Call an APIGet ContentDecideWaitRepeatRemixed Workflow
Integrations
AviatoGitHubGmailGoogle CalendarGoogle DocsGoogle DriveGoogle SheetsSlack

Platform status

Checking platform status
Block reference

Merge

Combines multiple data streams into one unified output.

Audience

Workflow creators.

Overview#

Combines multiple data streams into one unified output.

Use this block when its responsibility is clear in the graph. Give it a name that describes the work it performs, then test it with representative input before publishing.

Working examples#

These are complete starting points, not decorative diagrams. Every graph is also available in the main template library and is checked by the workflow compiler.

1. Compare two research briefs#

You will build: One payload containing both research briefs.

Preserves both sources before synthesis. Named inputs make source order visible and reproducible.

Compare two research briefs
One payload containing both research briefs
Use template
Press enter or space to select a node. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

Open this template and adapt the labels, prompts, or credentials to your own workflow.

2. Join brand voice and campaign goal#

You will build: One brief with voice and campaign constraints.

Prevents either set of constraints from being lost. The merge is deterministic and does not rewrite either input.

Join brand voice and campaign goal
One brief with voice and campaign constraints
Use template
Press enter or space to select a node. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

Open this template and adapt the labels, prompts, or credentials to your own workflow.

3. Unify customer and order context#

You will build: A single support-case payload.

Makes downstream triage operate on the same case context. Separate ports keep customer and order records distinguishable.

Unify customer and order context
A single support-case payload
Use template
Press enter or space to select a node. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

Open this template and adapt the labels, prompts, or credentials to your own workflow.

Ports#

  • Input: in 1 (in-1): any, optional, single. Legacy aliases: in1.
  • Input: in 2 (in-2): any, optional, single. Legacy aliases: in2.
  • Input: in 3 (in-3): any, optional, single. Legacy aliases: in3.
  • Input: in 4 (in-4): any, optional, single. Legacy aliases: in4.
  • Input: in 5 (in-5): any, optional, single. Legacy aliases: in5.
  • Input: in 6 (in-6): any, optional, single. Legacy aliases: in6.
  • Input: in 7 (in-7): any, optional, single. Legacy aliases: in7.
  • Input: in 8 (in-8): any, optional, single. Legacy aliases: in8.
  • Input: in 9 (in-9): any, optional, single. Legacy aliases: in9.
  • Input: in 10 (in-10): any, optional, single. Legacy aliases: in10.
  • Output: Data (out): any, optional, single. Legacy aliases: out-right.
  • Dynamic inputs: inputCount selects 2 to 10 in-N ports; default 3.

Inspector#

  • Inputs: key inputCount; number; range: 2 to 10; default: 3.
  • Merge Mode: key mode; select; options: text, array, object, first; default: "text".

Behavior#

  • Input requirement: At least 2 inbound connections are required.
  • Execution: Handled by the handler using merge.
  • Timeout: No node-level timeout is defined.

Cost#

Uses workflow compute and may contribute to the run's compute cost.

Security#

  • No credentials are used.
  • The node has no external side effects.

Retry#

The runtime may retry this node according to the compiled execution policy.

Production checklist#

  • Test the happy path and one malformed or empty input.
  • Keep credentials out of prompts and published graph configuration.
  • Set a timeout and retry policy that matches the operation's side effects.
  • Name the final result so a runner can tell what success looks like.

Was this useful?

Your response helps us improve the documentation.

More blocks

Ask for Input

Ask one question or collect several related answers when the workflow starts.

Generate Text

Generate text with GPT, Claude, or Gemini.

Generate Image

Generate images with Gemini or OpenAI.

On this page
OverviewWorking examples1. Compare two research briefs2. Join brand voice and campaign goal3. Unify customer and order contextPortsInspectorBehaviorCostSecurityRetryProduction checklist
© 2026 Edge Platforms, Inc. All rights reserved.