CRMFile or API
Customer record import
Map approved customer fields into a first CRM workflow.
Scope this workflowConnect with a clear purpose.
Unified connection work is scoped around available documentation, permitted access, and a testable outcome. These examples help frame a conversation; they are not a partner directory or a guarantee of synchronization.
Scoping directory
Find an example close to your workflow.
Search by task, information, or connection path. Availability is confirmed only after review and testing.
9 examples
CRMEmail, form, or API
Support intake
Scope how an incoming request becomes owned work with customer context.
Scope this workflowCRMApproved file access
Customer file reference
Define which files can be referenced from a customer record and who may open them.
Scope this workflowCRMAPI or export
Invoice status handoff
Bring the billing status needed for a customer workflow into view.
Scope this workflowPOSManual outcome recording
External payment terminal
Record the outcome supplied by an external terminal without claiming to process the payment.
Scope this workflowPOSFile import
Catalog setup
Review a product export and map the fields needed by a local POS station.
Scope this workflowPOSLocal export
Register report export
Define a local report that can be handed to an approved back-office process.
Scope this workflowLumaAuthenticated network access
CRM context in Luma
Evaluate a signed-in Windows workflow that reads approved CRM context when the network is available.
Scope this workflowLumaLocal file workflow
Office file exchange
Scope how documents, sheets, or presentations enter and leave an evaluated Luma workflow.
Scope this workflowConnection review
A useful connection has a specific boundary.
Name the information
Identify the records and fields the workflow needs, along with the source of truth.
Approve the access
Use the narrowest available method and confirm who can read, change, or export data.
Test the outcome
Verify the happy path, failure handling, and ownership before expanding the scope.
Plan the next step
Bring the workflow, not a logo list.
Share the task, the systems involved, and what should happen when the connection is unavailable.