Calendar-managed execution
Manage scheduled workflow starts from a platform calendar instead of burying timing rules inside each flow.
Schedule trigger
Schedule for customer-owned automation.
Use the Schedule trigger when a CXFabric Schedule should start one or more flows at planned times.
Start flows from configured CXFabric Schedules managed in the platform calendar.
Schedule
Trigger
ScheduleConfigured Schedules start one or more flows from the CXFabric platform calendar.
CX
CXFabric Flow
Rules, credentials, validation, audit
SettingsInputs and options
LogsRun history and output
Next stepConnector, component, or approval
What this component unlocks
Use Schedule as a visible flow step.
The CXFabric Schedules area provides a visual calendar for viewing upcoming scheduled workflow runs, creating new schedules, and managing existing schedules. Schedules can be one-time, recurring, or paused/disabled, and users can edit, delete, enable, or disable schedules based on their role permissions.
One-time and recurring schedules
Support single future runs and repeated execution patterns for operational automation.
Enable and disable control
Pause a schedule without deleting it, then reactivate it when the workflow should run again.
Use cases
Where Schedule fits in automation.
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Daily customer sync
Use Schedule as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Nightly reporting
Use Schedule as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Reminder delivery
Use Schedule as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Scheduled cleanup
Use Schedule as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Recurring polling workflow
Use Schedule as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Operational health check
Use Schedule as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Configuration surface
Practical options builders expect to use.
The exact fields can vary by deployment and product version, but each page gives customers a clear view of the component's intended role.
View schedules on a calendar
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Create a new schedule
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Set one-time or recurring behavior
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Review upcoming events
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Edit schedule details
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Enable, disable, or delete schedules
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Implementation notes
Design the step with operations in mind.
Components should be easy for builders to configure and easy for operators to understand after the workflow is live.
Current CXFabric docs
Use clear names so upcoming events are easy to recognize
Use clear names so upcoming events are easy to recognize.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Role permissions determine which schedules and actions a user can access
Role permissions determine which schedules and actions a user can access.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Use paused or disabled schedules when timing should stop temporarily without losing the schedule definition
Use paused or disabled schedules when timing should stop temporarily without losing the schedule definition.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Workflow patterns
Reusable patterns for Schedule.
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Schedule in a customer intake flow
Start with an event, use Schedule, then route the result to CRM, ticketing, or a customer-owned system.
Schedule with approval and audit
Add validation, human approval, and logging around the component before downstream actions execute.
Schedule in a private runtime
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Schedule plus custom connector
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
Need Schedule inside a customer workflow?
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.