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 ProcessFlow is the primary unit of work in APPSeCONNECT. It defines how data moves from a source application to a destination application. Every integration is made up of one or more ProcessFlows.
Key nodes in a ProcessFlow:
| Node | Purpose |
| APP (GET) | Fetches data from the source application (e.g., orders from Shopify) |
| APP (POST) | Sends data to the destination application (e.g., creates order in SAP) |
| MAPPER | Transforms and maps fields between source and destination schemas |
| DECISION | Filters records based on conditions (e.g., only sync Paid orders) |
| SPLITTER | Breaks a batch of records into individual records for processing |
| MERGER | Combines multiple records into a single payload |
| DELAY | Pauses execution for a specified time (useful for rate limiting) |
| RETURN RESPONSE | Captures and logs sync results in Snapshot and Sync Info |
How to create a ProcessFlow:
Go to ProcessFlow in the left navigation.
Click New ProcessFlow.
Give it a descriptive name (e.g., 'Shopify to SAP B1 — Order Sync').
Drag and connect nodes from the left panel to the canvas.
Configure each node: select the app, choose the operation (GET/POST), and map the fields.
Add a RETURN RESPONSE node at the end.
Click Save, then Deploy.
2. The MAPPER Node — Field Mapping
The MAPPER is where you define how fields from the source app translate to fields in the destination app. It is the most configuration-intensive node in APPSeCONNECT.
How to map a field:
Open the MAPPER node by double-clicking it on the canvas.
On the left, you see the destination app's schema. On the right, the source app's schema.
Drag a source field to a destination field to create a mapping.
To add a transformation: click the mapped field and enter a transformation expression (e.g., #(quantity, 1) to default nulls to 1).
To add a constant value: type the value directly instead of dragging a source field.
Save the MAPPER when done.
Common MAPPER transformations:
| Transformation | Example | Effect |
| #(field, default) | #(quantity, 1) | Returns 1 if quantity is null |
| uppercase(field) | uppercase(sku) | Converts SKU to uppercase |
| concat(a, b) | concat(firstname, lastname) | Combines two fields |
| replace(field, old, new) | replace(phone, '-', '') | Removes hyphens from phone |
| substring(field, start, len) | substring(postcode, 0, 5) | Extracts first 5 chars |
3. Snapshot — Understanding Sync Results
The Snapshot gives you a record-by-record view of what happened during each ProcessFlow execution.
How to read Snapshot:
Green record: Successfully synced.
Red record: Failed. Click to see the exact error message and the data payload that caused the failure.
Yellow record: Partially processed — some data synced, some did not.
Empty Snapshot: RETURN RESPONSE node is missing — add it and redeploy.
How to resync a failed record:
Open Snapshot for the relevant execution.
Click the red record.
Review the error. Fix the underlying issue (data or connection).
Click Resync on that specific record.
How to export Snapshot data:
In Snapshot view, click the Export button (CSV).
The CSV includes record IDs, sync status, timestamps, and error messages.
Attach this CSV when raising a support ticket for faster resolution.
4. App Resource and Schema Management
The App Resource defines the data schema — the fields — that APPSeCONNECT knows about for each connected application. When you add a new custom field in your app (e.g., a UDF in SAP or a metafield in Shopify), you must also add it to the App Resource schema in APPSeCONNECT before it can be mapped.
How to add a custom field to the schema:
Go to Apps > My Apps and select the relevant app.
Click App Resource.
Select the resource type (e.g., Sales Order, Customer).
Click Edit Schema.
Click Add Field. Enter the field name exactly as it appears in the API (e.g., U_WebOrderID for a SAP UDF).
Set the data type (String, Integer, Boolean, etc.).
Save. The field is now available in the MAPPER.
5. Sync Info — Monitoring and Auditing
Sync Info provides an aggregate view of all sync activity — how many records were processed, succeeded, and failed across all executions of a ProcessFlow.
Key metrics in Sync Info:
| Metric | What it means |
| Total Records | All records fetched from the source in this execution |
| Succeeded | Records successfully created/updated in the destination |
| Failed | Records that errored — click to open Snapshot for details |
| Skipped | Records excluded by a DECISION node filter |
How to filter Sync Info:
In Sync Info, use the date range picker to narrow to a specific period.
Use the search box to find a specific record by source ID or destination ID.
Filter by status (Success, Failed, Skipped) to focus on specific record types.
6. Real-Time ProcessFlows (Webhook Triggers)
Real-time ProcessFlows execute immediately when an event occurs in the source application — for example, a new order placed in Shopify triggers the flow within seconds rather than waiting for the next scheduled run.
How to set up a real-time flow:
Create or open a ProcessFlow.
In the APP (GET) node, set the trigger type to 'Real-Time / Webhook'.
After saving, deploy the ProcessFlow. APPSeCONNECT generates a webhook URL.
Copy the webhook URL from the Deployment panel.
In your source application (e.g., Shopify > Settings > Notifications > Webhooks), add a new webhook pointing to the APPSeCONNECT URL.
Select the event type (e.g., 'Order creation').
Test by placing a test order — it should appear in Snapshot within seconds.
NOTE: Real-time flows require the On-Premise Agent's InSync Service to be running (for On-Premise setups). If the service is stopped, incoming webhook events queue until the service restarts.
7. Scheduled ProcessFlows
Scheduled flows run at fixed intervals — every 15 minutes, hourly, daily, etc. They are best for batch operations like inventory sync, price updates, and shipment tracking updates.
How to configure a schedule:
Open the ProcessFlow.
In the APP (GET) node, set trigger type to 'Scheduled'.
Set the interval (e.g., every 30 minutes).
APPSeCONNECT uses UTC for all scheduling. Convert your desired local time to UTC before setting.
Deploy the ProcessFlow. The first run happens at the next scheduled interval.
8. Environments and Agent Management
APPSeCONNECT supports multiple environments — typically Production and a Test/Staging environment. Each environment has its own agent (Cloud or On-Premise) and its own deployed ProcessFlows.
Best practices:
Always test new ProcessFlows in a staging environment before deploying to production.
Keep the On-Premise Agent updated — check for new versions in Settings > Agent Download.
Monitor agent status daily in Environments — a red/orange status requires immediate attention.
For SAP B1: ensure the DI Server and SLD services are configured to start automatically on Windows (set to 'Automatic' startup in services.msc).
9. DECISION Node — Filtering Records
The DECISION node filters records based on conditions you define. Only records that match the condition pass through to the next node. Records that don't match are logged as Skipped in Sync Info.
Common use cases:
Sync only orders with status = 'Paid' (skip Pending and Cancelled).
Exclude test orders (e.g., order total = 0).
Skip records that already have an SAP ID (to prevent duplicates).
Route different order types to different destination nodes.
How to configure a DECISION node:
Drag a DECISION node onto the canvas and connect it after the GET node.
Double-click to open the configuration.
Set the condition: select the field, operator (equals, contains, greater than, etc.), and value.
Connect the TRUE output to the next processing node.
Optionally connect the FALSE output to a RETURN RESPONSE node to log skipped records.
10. SPLITTER and MERGER Nodes
SPLITTER: Takes a batch (array) of records and splits it into individual records for processing one by one. Use this when the destination app only accepts one record at a time (e.g., SAP DI API creates one order per call).
MERGER: Combines individual records into a batch before sending to the destination. Use this when the destination accepts bulk payloads (e.g., bulk product import to Shopify).
11. Notifications and Alerts
How to set up email alerts for sync failures:
Go to Settings > Notifications.
Click Add Notification Rule.
Select the event type: Sync Failure, Agent Offline, or Connection Error.
Enter the email address(es) to notify.
Set the threshold (e.g., alert after 5 consecutive failures to avoid noise).
Save.
TIP: Set up notifications for Agent Offline events — these are easy to miss and can cause hours of unprocessed data if not caught quickly.
12. User Management and Roles
Available roles in APPSeCONNECT:
| Role | Access |
| Admin | Full access: manage users, billing, all configurations |
| Integration Manager | Create/edit/deploy ProcessFlows; manage connections; view billing |
| Developer | Create/edit ProcessFlows and schemas; cannot manage users or billing |
| Viewer | View-only: see Sync Info, Snapshots, and ProcessFlow status |
How to invite a new user:
Go to Settings > Users.
Click Invite User.
Enter the email address and select a role.
Click Send Invitation. The user receives an email with a link (valid 48 hours).
Once accepted, the user can log in and access features based on their role.
13. Integration Templates (Pre-Built Flows)
APPSeCONNECT provides pre-built integration templates for common use cases. Templates include all the standard ProcessFlows for a given app pair (e.g., Shopify ↔ SAP B1) with standard field mappings already configured.
How to use a template:
Go to ProcessFlow > Templates.
Search for your app combination (e.g., 'WooCommerce SAP').
Click Use Template.
The template flows are copied to your account.
Review and customise the MAPPER for your specific field mappings and business rules.
Validate connections, then deploy.
NOTE: Templates provide a starting point — always review the MAPPER before deploying. Your SAP configuration (Item Codes, BP Codes, Price Lists, Warehouses) will differ from the template defaults.
14. Multi-Environment Management
Enterprises with multiple SAP companies or multiple eCommerce stores can manage them all from a single APPSeCONNECT account using separate environments.
Create a separate environment for each SAP company or store: Settings > Environments > Add Environment.
Deploy different ProcessFlows to different environments as needed.
Each environment has its own agent — ensure the On-Premise Agent on each SAP server is linked to the correct environment.
Use environment labels (Production, Staging, UAT) to avoid accidental deployments to the wrong environment.