Setting Up Your First ProcessFlow

Setting Up Your First ProcessFlow

Audience: Administrators, integration developers

Applies to: All ProcessFlow-enabled plans

Last reviewed: 2026

1. Understanding ProcessFlow Nodes

Each node performs one function. Combine them left-to-right to create a complete data flow.

NodePurposeNotes
STARTEntry point for the flowRequired as the first node
APP (GET)Pulls data from source applicationE.g., fetch new Shopify orders
MAPPERTransforms and maps fields between schemasRequired between every GET-POST pair
APP (POST)Pushes data to destination applicationE.g., create SAP Sales Order
DECISIONRoutes flow based on a conditionE.g., skip if order total = 0
SPLITTERSplits a batch into individual itemsUse before per-record operations
RETURN RESPONSEReturns result data to calling systemREQUIRED at end of every flow

WARNING: Missing RETURN RESPONSE means Sync Info shows 0 records — impossible to audit or retry syncs.

2. Creating a ProcessFlow

  1. Navigate to ProcessFlow > Create New and give it a descriptive name.
  2. Drag START, APP (GET), MAPPER, APP (POST), RETURN RESPONSE onto the canvas and connect them left-to-right.
  3. Open the MAPPER and map source fields to destination fields.
  4. Click Save, then Deploy and select the target Environment.

3. Field Mapping Best Practices

  • Map all mandatory destination fields — check the destination app schema for required fields.
  • Use hardcoded default values for required fields with no source equivalent (e.g., Document Series in SAP B1).
  • Apply the '#' (hash) function in the mapper to handle null/empty source values — prevents null-to-integer errors.
  • For multi-store setups, use the DECISION node to route records by store identifier before mapping.
  • Test with 1-2 sample records before enabling auto-sync.

4. Scheduling and Triggers

Trigger TypeHow It Works
Auto Sync (Schedule)Runs at fixed interval (e.g., every 15 min). Set in flow Settings tab.
ManualAgent dashboard - select flow - Run Now. For one-off or test syncs.
WebhookExternal system calls APPSeCONNECT webhook URL to trigger instantly.
API CallTrigger via APPSeCONNECT REST API for custom orchestration.

5. Monitoring: Snapshots and Sync Info

Go to ProcessFlow > Snapshots to see real-time logs per node execution. Each row is one run — expand to see node results. Click a failed node for the error message and data payload. Use Resync to retry failed records without re-running the full flow.

Sync Info shows totals: records processed, success count, error count. Filter to errors only for quick diagnosis.

6. Common ProcessFlow Issues

SymptomRoot CauseFix
Sync Info shows 0 recordsMissing RETURN RESPONSE nodeAdd RETURN RESPONSE as final node
Orders not appearing in destinationGET node filter excluding recordsReview GET node filters; check date range and status filters
Duplicate records createdFlow triggered twice or lookup key not uniqueCheck schedule overlap; ensure unique lookup key
Mapping errors on numeric fieldsNull source value passed to integer fieldUse '#' function or hardcoded default in MAPPER
Flow not running on scheduleAgent offline or deployment not activeCheck Agent status; re-deploy the flow

    • Related Articles

    • Product Features & How-Tos

      Audience: All users Applies to: All plans Last reviewed: 2026 This article explains how to use APPSeCONNECT's core features and walks through common how-to tasks. Use it as a reference guide for day-to-day operation. 1. ProcessFlow — Core Concepts A ...

    • APPSeCONNECT Troubleshooting Guide

      Audience: All users — customers and CS/support teams Applies to: All integrations and environments Last reviewed: 2026 This guide covers the most frequent issues reported by APPSeCONNECT customers, organized by category. For each issue you will find: ...

    • Billing & Account Management

      Audience: Account administrators and billing contacts Applies to: All plans Last reviewed: 2026 This article covers billing, subscription management, plan changes, invoicing, and account administration for APPSeCONNECT. 1. Plans and Pricing Overview ...

    • Managing Environments and Agents

      Audience: Administrators, IT teams Applies to: All environments (Cloud and On-Premise) Last reviewed: 2026 1. Cloud vs. On-Premise Agent Factor Cloud Agent vs. On-Premise Agent Provisioned by APPSeCONNECT automatically | You (installed on your ...