Pull Changes
Pulling changes keeps your Nected workspace aligned with the latest state of your Git branch. After a pull request is merged in GitHub (or any direct commit lands on the branch), you use Pull in Nected to fetch and apply those updates to Rules, Workflows, Datasets, Integrations, Variables, and other Synced Entities.
Nected guides you through a four-step process so that:
All remote changes are discovered
Integrations and credentials are correctly mapped
Environment-specific configuration stays valid
The final merge into your workspace is safe and predictable
Accessing Pull
Select the branch you want to sync from the Git Repository panel.
Click Pull.
The Branch: <branch-name> → Pull dialog opens with a 4-step progress bar:
Check for Changes
Sync Integrations & Credentials
Update Missing Configs
Apply All Changes
The dialog walks you through each step in order.
Step 1 — Check for Changes
In this step, Nected compares your active branch in the workspace with the remote branch in Git.
Nected will:
Fetch the latest commit history from the remote branch.
Identify all Synced Entities that changed since your last pull:
Rules (including RuleSets and versions)
Workflows
Datasets
Variables
Other supported entities
Group changes by type with counts, for example:
44 Datasets Added (82 Versions)34 Rules Added (67 Versions)11 Workflows Added (16 Versions)8 Variables Added (8 Versions)
List each changed resource with a link or identifier so you can scan what will be updated.
If no changes are detected, the dialog shows “No changes found” and you can close the modal.
If changes exist, review the list to confirm that the incoming updates match what you expect from Git (for example, from your latest PR merge).
Once you are comfortable with the list of changes, proceed to the next step.
Step 2 — Sync Integrations & Credentials
Rules and workflows pulled from Git often depend on external systems (APIs, databases, queues, etc.). Their configuration lives in Integrations, and the actual secrets (API keys, tokens, passwords) are never stored in Git.
In this step, Nected ensures that:
Every Integration referenced by the incoming changes exists in your workspace.
Each Integration has valid credentials/configuration in the current environment.
Any new Integration references in Git are mapped to existing Integrations in Nected or marked as missing.
Typical actions you may perform here:
Map remote Integration references to existing Integrations in your workspace.
Create missing Integrations if a new connector was added in another environment.
Add or update credentials for Integrations that are missing required secrets.
This step prevents you from pulling logic that would break at runtime due to missing connectors or credentials. Once all Integration and credential issues are resolved, Nected marks this step as complete.
Step 3 — Update Missing Configs
Beyond Integrations and credentials, rules and workflows may rely on other environment-specific configuration, such as:
Data Source connections
Global Attributes/environment variables
API base URLs
Dataset connection details or schema-related settings
Scheduler or trigger configurations tied to external services
In this step, Nected:
Detects configuration items referenced by the incoming changes that do not yet exist or differ in your workspace.
Highlights what is missing or mismatched (for example, a dataset connection that doesn’t exist in this environment).
Lets you update or create these configs so that after the pull, everything remains executable.
You use this step to:
Align environment-specific resources (e.g., mapping a staging data source to the correct production equivalent).
Confirm that any new config added in Git is mapped correctly in the current workspace.
Only after all required configs are resolved does Nected allow you to move to the last step.
Step 4 — Apply All Changes
Once changes, integrations, credentials, and configs are validated, you apply the updates to your workspace.
Here you choose how Nected merges remote changes into your local state.
Merge & Pull
Use Merge & Pull when you want to:
Combine remote changes with your local workspace state.
Preserve both sets of changes where Nected can merge automatically.
Nected:
Applies all incoming changes to the corresponding entities.
Updates versions of Rules, Workflows, Datasets, and Variables.
Leaves your local workspace in sync with the remote branch.
Override & Pull (if available in your flow)
Use Override & Pull when you want to:
Discard local modifications in favour of the remote branch version.
Nected:
Replaces local entity definitions with the remote versions.
Aligns the workspace exactly with the branch state from Git.
Conflict Handling
If Nected detects conflicts that cannot be automatically merged, it:
Flags the affected resources.
Provides options like Override, Archive, or similar resolution actions (depending on the entity type and conflict).
Requires you to resolve conflicts before finishing the pull.
After you apply changes:
Nected shows a success message (for example, “All changes merge successfully”).
The Git panel status updates to reflect the new alignment state (no longer “Behind” for that branch).
Your workspace is now synchronized with the selected branch, and you can continue building on top of the latest logic.
Pulling regularly reduces conflicts and keeps everyone aligned with the agreed state of the automation logic.
Last updated