Ticketing Software Integration

Ever tried keeping Salesforce data in sync with an external system, only to run into polling delays, missed deletes, or performance bottlenecks? I’ve found Change Data Capture (CDC) to be a game-changer for event-driven integrations. With CDC, every record create, update, delete, or undelete fires a “change event” into Salesforce’s event bus. External systems subscribe once and get only the changes they need—no more round-the-clock polling. Some favorite use cases: Sales Cloud → ERP sync: Account and Opportunity changes flow in real time to your finance system. Service Cloud → Ticketing: Case updates automatically create or update tickets in Jira or ServiceNow. On-platform automation: Complex recalculations or external callouts happen asynchronously via CDC triggers, not inside the user’s save. Pro tip: Leverage the ChangeEventHeader—it tells you exactly which fields changed, when, and even who triggered the change. Use changeOrigin to avoid feedback loops when syncing bi-directionally. How are you using CDC in your org? Share your experiences or questions below!

One of iCIMS' biggest strengths is the powerful configurability of user dashboards. This week, I want to share a trick you might not realize is possible in the #iCIMS dashboard: You can embed a ticketing system, like Jira or Monday.com, directly into users' dashboards so they can contact your team without ever leaving the platform. We used Monday in this case to make it easier for our managed services customers to submit tickets from right inside iCIMS. Here’s how we did it: 1. Grab a shareable link from your Monday board (or Jira form) 2. Go to Report > Manage Dashboards in iCIMS 3. Create a new item with Type = Text 4. Create a sub-item and select Insert/edit media 5. In the General tab, paste the URL for the form You can adjust the size by unchecking “Constrain proportions” and tweaking the values. We used 600x600, which fits nicely in a three-column layout. Small tweaks like this can make a big difference in streamlining support and improving the user experience. Have you tried something similar? I’d love to hear how you're customizing your iCIMS setup!

Can I pipe BP notifications straight into ServiceNow? This question hits every Workday admin at some point... And the answer? -Not natively. -Not easily. -But definitely possible. Here’s how top-performing Workday teams are doing it in 2025...based on real-world fixes, not theory: ✅ Option 1: The Email-to-Ticket Workaround ->Fastest to set up. ->You configure a BP notification to go directly to ServiceNow’s inbound email address. 🔹 ServiceNow parses the email 🔹 Creates a ticket using custom rules 🔹 Minimal Workday config needed BUT… ->Breaks if email formats change ->Limited error handling ->Not ideal for high volume or sensitive data ->Good for small teams or quick wins ✅ Option 2: Native Integration via Workday Studio / Orchestrate ->The cleanest, most scalable approach. ->You build an event-driven integration that gets triggered automatically at a BP step or completion. 🔹 Workday sends real-time data via REST or SOAP 🔹 ServiceNow receives it as a structured ticket 🔹 Full context: worker, event, comments, etc. ->With Workday Orchestrate (2025R1), you can even build this as a low-code flow, no Studio needed. ->Best for real-time alerts in onboarding/offboarding ✅ Option 3: Use an iPaaS like Boomi, MuleSoft, or Make ->This is what most large enterprises do. ->The middleware acts as the bridge: 🔹 Receives BP event data (via API, email, or RaaS) 🔹 Transforms and maps fields 🔹 Sends formatted payload to ServiceNow ->Prebuilt connectors + retry logic = more stability, less stress. ->Ideal if your org already uses Boomi or MuleSoft ✅ Option 4: Daily Batch Sync (via Report-as-a-Service or EIB) ->If you don’t need real-time: 🔹 Create a custom report of completed BPs 🔹 Use RaaS or scheduled job to export it 🔹 ServiceNow ingests the data and opens tickets in bulk ->No need for complex triggers...just regular polling. ->Great for low-priority cases (compliance logs, onboarding prep, etc.) So... can you do it? Yes. But not out-of-the-box. You need to engineer your strategy based on urgency, volume, and tools.

STEAL THIS!! Week 9! S09. Managing Issues/Bugs in your Rocketlane project [Note: This is a series to share HRUR - How Rocketlane Uses Rocketlane. So you can borrow from our ideas and configurations!] Testing / UAT is a phase of a large implementation that can create anxiety for customers and implementation teams. We need to show intensity in how we track issues / bugs that come up in this period, provide visibility on their status, and win the customer confidence to go-lives faster. Here is how we do this at Rocketlane: We use a ‘Bug Reporting’ form as part of the project template. Customers can use the form to record any issues that they notice. This simple form contains questions such as - Title, Bug Description, Priority (P0/P1/P2,etc), Requester Name, Requester Email, and an ‘Attachment’ type question for any additional information to be provided. When this bug form is filled out and submitted, two things happen- 1. A ‘Task’ is created in Rocketlane and automatically categorised as a ‘Bug’. This is added as an ‘Ad-hoc’ task on the project, and does not show up on the main project plan, but can be accessed through saved views at the project level and globally. Rocketlane’s native automations can be used to set up this workflow. 2. A ‘Ticket’ is created on our support helpdesk, with the link to the task on the Rocketlane project. This is done through an integration that can be set up using Rocketlane’s native automations. We make sure to store the reference of the Task and Ticket in their respective systems so that we can facilitate downstream conversations between the two. We have a few more automations that help us facilitate updates between the Task in Rocketlane and the Ticket in the Helpdesk: 1. If the priority (P0/P1/P2,etc) is updated on the task, it also updates the same on the Helpdesk. This helps prioritise better, and SLAs are automatically applied on the ticket in the helpdesk. 2. If the status of the Helpdesk ticket is updated, it is mapped to the Rocketlane task status, and immediately the same. This reduces any delays or communication gap when a bug is resolved. This automation is set up through the Helpdesk’s native automations feature using APIs, but can also be done via Zapier or Workato. 3. Whenever a note is added on the Helpdesk ticket, it is sent to the ‘Chat’ section on the Rocketlane task and the task assignee gets an email notification about the update. This automation is also set up through the Helpdesk’s native automations feature, but can also be done via Zapier or Workato. Additionally, Users can keep a tab on Bugs across all their projects on the ‘All tasks’ page, by setting up a simple filtered view! Check out the screenshots below for an example of our Bug Reporting form, and the automation templates. Feel free to let us know if you’re interested in setting this up for your Rocketlane account, and someone from our team will be happy to help you out! h/t Shyam Karthik

Learn How Lead Love is Transforming Fan Engagement for Birmingham Legion FC! ⚽🚀 "Lead Love’s integration has enhanced our data management significantly. We now have a comprehensive view of our Ticketmaster data specific to ticket sales, attendance, and overall ticket revenue delivered directly into HubSpot. This functionality has enabled us to make data-driven decisions. The ability to determine event attendance & revenue also allows us to discern which of our marketing efforts work best with & for our fans." — Timothy Burke Sullivan, SVP, Corporate Sales and Strategy 🚀 The Journey: Birmingham Legion FC faced the all-too-common challenge of fragmented data—ticket sales, attendance, revenue, and customer info were all in separate silos. This made it tough to truly understand their fans or make informed decisions. Our Solution: We teamed up to integrate their HubSpot CRM with Ticketmaster's Archtics system. This one-way sync means all their crucial data now lives in one accessible place. The Amazing Results: 🎯 Smart Decisions Made Easy: Custom dashboards in HubSpot are now their go-to for insights on attendance, revenue, and engagement. 💡 Data-Driven Strategies: They're optimizing everything from sponsor seat distribution to marketing campaigns based on real metrics. 📨 Personalized Marketing: With attendance linked to customer data, they can now send targeted campaigns—like season ticket offers to fans who attend frequently. ⚙️ Efficient Operations: Sales and marketing teams are more aligned and efficient than ever. What's Next: Birmingham Legion FC is just getting started, they're planning to: 🔄 Boost Marketing Automation: Creating highly personalized workflows for different fan segments. 🏟️ Enhance Fan Experiences: Using data insights to improve everything from in-stadium services to personalized promotions. 📈 Maximize Season Ticket Sales: Leveraging data to identify potential season ticket holders and tailor offers they'll love. 🤝 Strategic Growth: Using business intelligence to make savvy decisions on partnerships and pricing. Stories like these are why I started Lead Love. It's not just about integrating systems; it's about empowering organizations to connect more deeply with their audiences and drive growth through data-driven insights. A huge shoutout to Timothy Sullivan and the entire Birmingham Legion FC team for embracing innovation and setting a new standard in fan engagement! #DigitalTransformation #DataAnalytics #CustomerExperience #DataDriven #MarketingAutomation #SportsMarketing #HubSpot #Ticketmaster #SportsBusiness #Ticketing #RevenueGrowth #FanEngagement #SportsTech, #CRMIntegration #RevenueOps #GrowthStrategy #BusinessIntelligence #OperationalEfficiency #HubSpotIntegration, #SalesAutomation #AnalyticsInsights #SoftwareIntegration #CustomerRetention #TeamCollaboration #MarketingOps #BusinessScalability #BusinessInnovation