rConfig V8 Custom Workflows for Service Providers

rConfig V8 Custom Workflows for Service Providers

Custom Workflows transform rConfig V8 into a comprehensive network service automation platform for Internet Service Providers (ISPs), Managed Service Providers (MSPs), and telecommunications operators. Replace fragmented scripts, disconnected Ansible playbooks, and manual processes with integrated, repeatable workflows that automate customer onboarding, site deployment, VPN provisioning, and CPE configuration—all within rConfig’s unified management interface. Combine workflow automation with the REST API overview and Custom Commands capabilities to extend orchestration across your toolchain.

Developed by rConfig Professional Services, Custom Workflows provide enterprise-grade automation tailored to your specific service delivery model, reducing deployment times from hours to minutes while eliminating configuration errors and improving operational consistency.

Note

Custom Workflows are available exclusively through rConfig Professional Services. Contact our team to discuss your network automation requirements and receive a customized proposal.

Why Service Providers Choose Custom Workflows

Faster service activation: Reduce customer site deployment from 4+ hours to under 15 minutes with automated workflows.

Eliminate configuration errors: Standardized, tested workflows ensure consistent configurations across all customer sites.

Scale operations efficiently: Deploy hundreds of customer sites without proportionally increasing engineering headcount.

Reduce operational costs: Automate repetitive tasks, freeing engineers to focus on strategic initiatives and complex problem-solving.

Improve customer satisfaction: Deliver faster service activation with predictable, reliable deployment processes.

Maintain compliance: Ensure all customer deployments meet regulatory requirements and internal security policies.

Version control and audit trails: Track all workflow executions with comprehensive logging for troubleshooting and compliance.

Common Service Provider Use Cases

Customer Site Provisioning

Automate new customer onboarding workflows:

• Provision customer edge routers (CE) with standardized configurations
• Deploy site-specific VLANs, IP addressing, and routing policies
• Configure QoS policies based on customer service tier
• Enable monitoring and alerting for new customer equipment
• Generate as-built documentation automatically

Example workflow: “Deploy Enterprise Customer Site”

1. Input: Customer name, site address, bandwidth package, VLAN IDs
2. Provision CE router from template with customer-specific variables
3. Configure VPN tunnel to customer headquarters
4. Deploy site-specific firewall rules and access control lists
5. Enable SNMP monitoring and set alert thresholds
6. Generate and email deployment report to operations team

VPN Tunnel Deployment

Streamline VPN provisioning across multiple vendors:

• Deploy IPsec site-to-site VPN tunnels in minutes
• Configure GRE, DMVPN, or SD-WAN overlay networks
• Implement multi-vendor VPN environments (Cisco, Juniper, Fortinet, Palo Alto)
• Automate encryption policy, phase 1/2 parameters, and pre-shared keys
• Verify tunnel establishment and routing convergence

Example workflow: “Deploy IPsec VPN Tunnel”

1. Input: Site A device, Site B device, encryption profile, subnet information
2. Generate unique pre-shared key and store securely in vault
3. Configure IPsec policy on both endpoints
4. Deploy crypto maps and tunnel interfaces
5. Configure routing protocol over tunnel (OSPF, BGP, static)
6. Verify tunnel status and test connectivity
7. Update network documentation and CMDB

CPE Configuration Management

Automate customer premises equipment deployment:

• Zero-touch provisioning for customer-owned equipment
• Standardize CPE configurations across device models and vendors
• Deploy firmware updates across customer fleet
• Implement configuration templates with customer-specific variables
• Remote troubleshooting and configuration rollback capabilities

Example workflow: “Provision Customer CPE”

1. Input: Customer ID, device serial number, service package
2. Retrieve customer-specific configuration from template
3. Apply QoS policies based on service tier
4. Configure WAN interface with ISP-provided addressing
5. Deploy LAN-side DHCP, DNS, and default gateway
6. Enable remote management and monitoring
7. Validate configuration and connectivity
8. Send activation notification to customer

Multi-Site Service Deployment

Deploy services across distributed customer locations:

• Provision MPLS L3VPN customer sites
• Configure SD-WAN overlays for enterprise customers
• Deploy multi-site firewall policies consistently
• Implement hub-and-spoke or full-mesh topologies
• Coordinate configuration changes across multiple devices

Example workflow: “Deploy Multi-Site MPLS L3VPN”

1. Input: Customer VRF name, list of site addresses, routing protocol
2. Configure provider edge (PE) routers with customer VRF
3. Provision customer edge (CE) routers at each site
4. Deploy routing protocol (BGP, OSPF) between CE and PE
5. Configure route targets and import/export policies
6. Verify routing table convergence across all sites
7. Test inter-site connectivity
8. Generate service activation report

Network Change Automation

Implement repeatable change management workflows:

• Deploy scheduled maintenance windows across customer base
• Implement emergency change procedures with approval gates
• Roll back failed changes automatically
• Coordinate multi-device configuration changes
• Verify change success before and after deployment

Example workflow: “Emergency Firewall Rule Deployment”

1. Input: ACL name, source/destination IPs, ports, action
2. Request approval from change manager (optional)
3. Backup current firewall configuration
4. Deploy new ACL rule across all customer firewalls
5. Verify rule is active and traffic is flowing correctly
6. If verification fails, automatically roll back changes
7. Send deployment status notification to operations team
8. Update change management system with results

Service Decommissioning

Automate customer offboarding and equipment reclamation:

• Remove customer-specific configurations from network devices
• Deactivate VPN tunnels and routing policies
• Reclaim IP address allocations
• Disable monitoring and alerting for decommissioned services
• Generate final service report for billing and compliance

Example workflow: “Decommission Customer Site”

1. Input: Customer ID, site identifier
2. Backup all configurations for archival
3. Remove customer VLANs and routing policies
4. Deactivate VPN tunnels to customer site
5. Remove firewall rules and access control lists
6. Disable monitoring and alerting
7. Update IPAM with reclaimed IP addresses
8. Generate decommissioning report for finance and compliance

Custom Workflow Architecture

Custom Workflows combine native automation blocks with reusable script logic powered by the Script Integration Engine (SIE), allowing teams to embed complex decisioning without leaving rConfig.

Workflow Components

Triggers: Initiate workflows based on events or schedules

• Manual execution via web interface or API
• Scheduled execution at defined intervals
• Event-driven triggers (device status change, compliance violation)
• API webhook triggers from external systems

Actions: Execute tasks on devices or external systems

• Device configuration deployment
• Command execution and output parsing
• API calls to third-party systems (IPAM, ticketing, billing)
• Data transformation and validation
• Email notifications and reporting

Decision Logic: Implement conditional processing

• If/then/else branching based on device responses
• Loop constructs for multi-device operations
• Error handling and rollback procedures
• Approval gates for change management
• Variable substitution and templating

Integration Points: Connect with external systems

• IPAM systems (Infoblox, NetBox, phpIPAM)
• Ticketing platforms (Jira, ServiceNow, Zendesk)
• Billing systems and CRM platforms
• Authentication services (RADIUS, TACACS+, LDAP)
• Monitoring systems (Zabbix, PRTG, SolarWinds)
• Configuration management databases (CMDBs)

Workflow Execution Flow

1. Trigger: Workflow initiated by user, schedule, or event
2. Input Validation: Verify all required parameters are provided
3. Pre-Execution Checks: Validate device connectivity and prerequisites
4. Action Execution: Perform configuration changes sequentially or in parallel
5. Verification: Confirm changes were applied successfully
6. Rollback (if needed): Revert changes if verification fails
7. Post-Execution Tasks: Update documentation, send notifications
8. Audit Logging: Record all actions for compliance and troubleshooting

Benefits Over Traditional Approaches

Replacing Discrete Scripts

Traditional approach: Collection of bash, Python, or Expect scripts scattered across engineering workstations

• Pain points: Version control issues, no centralized management, difficult to troubleshoot, inconsistent execution
• Custom Workflows solution: Centralized workflow repository with version control, role-based access, comprehensive logging, and consistent execution environment

Replacing Ansible Playbooks

Traditional approach: Ansible playbooks for network automation requiring specialized DevOps knowledge

• Pain points: Complex setup, inventory management overhead, playbook development requires coding skills, limited integration with network management platforms
• Custom Workflows solution: GUI-based workflow builder, integrated device inventory, visual workflow design, native integration with rConfig device management

Replacing Manual Processes

Traditional approach: Step-by-step runbook procedures executed manually by engineers

• Pain points: Human error, inconsistent execution, slow deployment times, scalability limitations, knowledge silos
• Custom Workflows solution: Automated, repeatable processes with built-in error handling, rapid deployment, unlimited scalability, documented procedures accessible to entire team

Real-World Performance Improvements

ISP Customer Provisioning

Before Custom Workflows:

• Average deployment time: 4-6 hours per site
• Configuration errors: 15% of deployments require rework
• Engineer capacity: 3-5 sites per day per engineer
• Customer satisfaction: 72% activation SLA achievement

After Custom Workflows:

• Average deployment time: 12-18 minutes per site
• Configuration errors: < 1% deployment error rate
• Engineer capacity: 20-30 sites per day per engineer
• Customer satisfaction: 98% activation SLA achievement

MSP VPN Deployment

Before Custom Workflows:

• VPN tunnel provisioning: 2-3 hours including testing
• Configuration mistakes requiring remediation: 20%
• Documentation lag time: 1-2 days
• Revenue recognition delay: 3-5 business days

After Custom Workflows:

• VPN tunnel provisioning: 8-12 minutes end-to-end
• Configuration mistakes: < 2%
• Documentation generated: Immediate (automated)
• Revenue recognition: Same business day

Telecommunications CPE Management

Before Custom Workflows:

• CPE configuration updates: 30-45 minutes per device
• Firmware upgrade success rate: 85% first attempt
• Customer-impacting change windows: 4+ hours
• Operations team burnout: High (repetitive tasks)

After Custom Workflows:

• CPE configuration updates: 3-5 minutes per device
• Firmware upgrade success rate: 99% first attempt
• Customer-impacting change windows: < 30 minutes
• Operations team satisfaction: Improved (focus on complex work)

Development and Deployment Process

Phase 1: Discovery and Requirements (1-2 weeks)

Requirements gathering workshops:

• Document current manual processes and pain points
• Identify high-value workflows for automation
• Define success criteria and ROI expectations
• Map integration requirements with existing systems

Deliverables:

• Requirements specification document
• Workflow design mockups
• Integration architecture diagram
• Project timeline and milestones

Phase 2: Design and Prototyping (2-3 weeks)

Workflow architecture design:

• Design workflow logic and decision trees
• Define input parameters and validation rules
• Specify integration points and API requirements
• Create error handling and rollback procedures

Prototype development:

• Build proof-of-concept workflow
• Test with sample devices in lab environment
• Validate integration with external systems
• Demonstrate prototype to stakeholder team

Deliverables:

• Technical design document
• Working prototype workflow
• Integration testing results
• Revised timeline based on feedback

Phase 3: Development and Testing (4-6 weeks)

Production workflow development:

• Implement all workflow actions and logic
• Develop device configuration templates
• Build integration modules for external systems
• Create user interface components

Comprehensive testing:

• Unit testing of individual workflow actions
• Integration testing with production-like devices
• Load testing with multiple concurrent workflows
• Security testing and vulnerability assessment
• User acceptance testing with operations team

Deliverables:

• Production-ready workflows
• Comprehensive test results
• Security audit report
• User acceptance sign-off

Phase 4: Deployment and Training (1-2 weeks)

Staged production rollout:

• Deploy workflows to production rConfig environment
• Configure integration with external systems
• Set up monitoring and alerting
• Create rollback procedures

Team enablement:

• Administrator training on workflow management
• Operator training on workflow execution
• Troubleshooting procedures and documentation
• Knowledge transfer sessions

Deliverables:

• Production deployment confirmation
• Administrator documentation
• User training materials
• Support contact procedures

Phase 5: Optimization and Support (Ongoing)

Post-deployment support:

• 30-day intensive support period
• Performance monitoring and optimization
• Bug fixes and minor enhancements
• Workflow usage analytics and reporting

Continuous improvement:

• Quarterly workflow performance reviews
• Enhancement requests and feature additions
• Version compatibility updates
• Best practices sharing and optimization recommendations

Deliverables:

• Monthly support reports
• Performance analytics dashboard
• Enhancement roadmap
• Knowledge base articles

Technical Capabilities

Multi-Vendor Support

Custom Workflows support comprehensive multi-vendor network environments:

Routing platforms: Cisco IOS/XE/XR, Juniper JunOS, Arista EOS, Nokia SR OS, Huawei VRP

Firewall platforms: Palo Alto, Fortinet FortiGate, Cisco ASA/FTD, Check Point, Juniper SRX

Switching platforms: Cisco Catalyst, Arista, Juniper EX, HP/Aruba, Dell

Wireless platforms: Cisco WLC, Aruba, Ruckus, Ubiquiti

SD-WAN platforms: Viptela, Meraki, Fortinet, VeloCloud, Silver Peak

Workflow Capabilities

Configuration management:

• Template-based configuration generation with variable substitution
• Configuration snippets and modular building blocks
• Configuration validation before deployment
• Automatic configuration backup before changes
• Rollback to previous configuration on failure

Device operations:

• Execute CLI commands with output parsing
• File transfer (SCP, TFTP, FTP) for firmware and configurations
• Reboot and reload operations with safety checks
• Interface state management (shutdown, no shutdown)
• Verification commands post-deployment

Data operations:

• Parse device output with regex and structured parsing
• Variable storage and manipulation across workflow steps
• Integration with external data sources (APIs, databases)
• Template rendering with customer-specific data
• Export workflow results to CSV, JSON, or PDF

Error handling:

• Try-catch exception handling for graceful failures
• Automatic retry logic with exponential backoff
• Conditional rollback based on verification results
• Alert notifications for workflow failures
• Detailed error logging for troubleshooting

Security and Compliance

Access control:

• Role-based access control for workflow execution
• Approval gates for sensitive operations
• Audit logging of all workflow executions
• Credential management with encryption at rest
• Session logging for compliance

Change management:

• Integration with change management systems
• Maintenance window scheduling and validation
• Risk assessment and impact analysis
• Emergency change procedures with expedited approval
• Change documentation and reporting

Compliance features:

• Pre-deployment compliance checks
• Configuration validation against security policies
• Regulatory compliance reporting (PCI-DSS, HIPAA, SOC 2)
• Data retention policies for audit trails
• Encrypted communication with network devices

Integration Ecosystem

IPAM Integration

Automate IP address management within workflows:

Infoblox: Allocate IP addresses, create DNS records, manage DHCP scopes

NetBox: Query available IP space, update device IP assignments, sync rack elevations

phpIPAM: Reserve IP addresses, update subnet utilization, generate IP documentation

Ticketing System Integration

Coordinate workflows with service desk operations:

ServiceNow: Create incidents, update service requests, close change tickets

Jira Service Management: Open provisioning tasks, track workflow progress, update project boards

Zendesk: Create customer notification tickets, update support cases, escalate failures

Billing and CRM Integration

Streamline service activation and revenue recognition:

Salesforce: Update opportunity status, trigger billing activation, record service details

Zuora: Create subscriptions, activate billing, update service inventory

Custom billing platforms: API integration for service activation and usage reporting

Monitoring Integration

Enhance visibility and proactive management:

Zabbix: Add devices to monitoring, set alert thresholds, create service dependencies

PRTG: Configure sensors, define monitoring templates, set notification rules

SolarWinds: Add nodes to monitoring, configure polling, create custom dashboards

Authentication Integration

Centralize user authentication and authorization:

Active Directory/LDAP: Authenticate users, query group memberships, validate permissions

RADIUS/TACACS+: Coordinate device access with centralized AAA

SAML/OAuth: Integrate with single sign-on providers for workflow access

Pricing and Investment

Custom Workflows are priced based on complexity, number of workflows, and integration requirements:

Typical Investment Range

Starter Package:

• 2-3 automated workflows
• Single vendor/platform focus
• Basic integration (1-2 external systems)
• 30-day post-deployment support
• Standard documentation and training

Professional Package:

• 5-8 automated workflows
• Multi-vendor environment support
• Comprehensive integration (3-5 external systems)
• 90-day post-deployment support
• Advanced training and optimization

Enterprise Package:

• 10+ automated workflows
• Complex multi-vendor/multi-site environments
• Extensive integration ecosystem
• 6-month post-deployment support
• Dedicated customer success manager
• Quarterly optimization reviews

Return on Investment

Most service providers achieve ROI within 6-12 months through:

Operational efficiency: 70-85% reduction in deployment time Error reduction: 90%+ decrease in configuration mistakes Capacity expansion: 4-6x increase in engineer productivity Revenue acceleration: Faster service activation and billing recognition Customer satisfaction: Improved SLA achievement and customer retention

Getting Started

Step 1: Schedule Discovery Call

Contact rConfig Professional Services to discuss your automation requirements:

Email: [email protected] Subject: “Custom Workflows - [Your Company Name]”

Include in your message:

• Brief description of your business (ISP, MSP, telco, etc.)
• Number of network devices under management
• Current deployment challenges and pain points
• Preferred contact method and availability

Step 2: Requirements Workshop

Participate in a 2-hour discovery session with our Professional Services team:

• Present current workflows and processes
• Identify high-priority automation opportunities
• Discuss integration requirements
• Review technical environment and constraints
• Define success criteria and timeline expectations

Step 3: Receive Proposal

Within 5 business days, receive a comprehensive proposal including:

• Recommended workflow automation roadmap
• Technical architecture and integration plan
• Development timeline with milestones
• Investment breakdown and payment schedule
• ROI projections and performance improvements

Step 4: Project Kickoff

Upon contract execution, begin the development process:

• Kick-off meeting with project team
• Access to staging environment for testing
• Regular status updates and milestone reviews
• Prototype demonstrations and feedback sessions
• Deployment planning and go-live coordination

Success Stories

Regional ISP: Customer Site Provisioning

Challenge: Manual customer site deployment taking 6+ hours with frequent configuration errors

Solution: Custom workflow automating CE router provisioning, VPN tunnel creation, and monitoring activation

Results:

• Deployment time reduced to 15 minutes
• Configuration errors eliminated (0 rework in first 90 days)
• Engineer capacity increased 300%
• Customer satisfaction improved from 68% to 96%

National MSP: Multi-Site SD-WAN Deployment

Challenge: Complex multi-vendor SD-WAN deployments requiring specialized expertise

Solution: Automated SD-WAN overlay provisioning across Cisco, Fortinet, and VeloCloud platforms

Results:

• Deployment time reduced from 8 hours to 45 minutes per site
• Consistent configurations across all vendor platforms
• 10x increase in deployment capacity
• $250,000 annual savings in engineering costs

Telecommunications Provider: CPE Management

Challenge: Managing 5,000+ customer CPE devices with manual configuration updates

Solution: Zero-touch provisioning workflows with automated firmware management

Results:

• CPE provisioning time reduced from 45 minutes to 4 minutes
• Firmware upgrade success rate improved to 99.5%
• Reduced customer-impacting maintenance windows by 80%
• Improved operational team satisfaction and reduced turnover

Frequently Asked Questions

Can workflows be modified after deployment?

Yes. rConfig Professional Services provides workflow source code and documentation. Your team can make minor modifications, or engage Professional Services for major enhancements.

What happens during rConfig version upgrades?

Workflows are designed for compatibility across rConfig versions. Professional Services provides upgrade testing and compatibility updates as needed under support agreements.

Can we start small and expand later?

Absolutely. Most customers begin with 2-3 high-value workflows and expand over time. Workflow architecture supports incremental additions without redesign.

How long does development typically take?

Simple workflows: 4-6 weeks. Complex multi-vendor workflows with extensive integrations: 8-12 weeks. Timeline depends on requirements complexity and integration scope.

Do we need DevOps expertise to use workflows?

No. Workflows are designed for network operations teams. Basic CLI knowledge is sufficient. No programming or DevOps experience required for execution.

What if we need changes to existing workflows?

Support agreements include minor modifications and bug fixes. Enhancement requests are quoted separately based on complexity. Most customers bundle enhancements into quarterly optimization cycles.

Can workflows run on schedules?

Yes. Workflows integrate with rConfig’s scheduled task system for automated recurring execution. Supports cron-style scheduling and maintenance window coordination.

How are credentials managed securely?

Workflows use rConfig’s encrypted credential vault. Support for HashiCorp Vault, CyberArk, and other enterprise credential management systems.

What if a workflow fails midway?

Workflows include comprehensive error handling and automatic rollback capabilities. Failed workflows generate detailed error reports for troubleshooting. Retry logic included for transient failures.

Can workflows be triggered by external systems?

Yes. Workflows can be initiated via rConfig REST API, allowing integration with ticketing systems, customer portals, and other business applications.

Related Documentation

• Script Integration Engine (SIE) - User-accessible scripting framework
• Custom Commands - Laravel Artisan command development
• REST API - Programmatic workflow execution
• Scheduled Tasks - Automating workflow execution
• Device Templates - Configuration template management
• Professional Services - Overview of consulting offerings

Contact Professional Services

Ready to transform your network operations with Custom Workflows?

📧 Email: [email protected] 📞 Phone: Available in customer portal 🌐 Web: https://www.rconfig.com/professional-services

Include “Custom Workflows” in your subject line and briefly describe your automation goals. Our Professional Services team responds within 24 business hours.

---

Custom Workflows are developed by rConfig Professional Services for Internet Service Providers, Managed Service Providers, telecommunications operators, and enterprises seeking to automate network service delivery, reduce operational costs, and improve customer satisfaction.