🎉🎉 🚀 October is Workato Community Month! 🤝💚 Hey Workato Rockstars! 🌟👋 We all started somewhere in our Workato journey. Some of us began as Individual Contributors 👨💻👩💻, building recipes, solving integration challenges, and automating workflows. But somewhere along the way, we started sharing our knowledge, helping others, and becoming Community Contributors 🌍💡. ✨ Now, it's time to share that journey! 🎬 🔥 Introducing the Workato Community Video Challenge! 🔥 Here's how we can make it happen 👇 🎥 Step 1: Create a short video (1–2 minutes) sharing your Workato journey. 💡 Step 2: Tell us: 🚀 How did your Workato journey begin? 🧑💻 How did you grow from an Individual Contributor to a Community Contributor? 🤝🏻 What inspired you to start sharing your knowledge and helping others? 🌟 What has being part of the Workato community meant to you? 📢 Step 3: Share your video here in the Slack channel and inspire others with your story! 🎯 The Twist — Challenge Someone! 🔥 After sharing your video, nominate another Workato community member by tagging them and challenging them to share their journey next! 🙌 Let's create a chain reaction of stories, inspiration, learning, and community spirit. 🔗💚 Remember, you don't need to be an expert or a famous community contributor to participate. Every journey matters, and your story might be exactly what inspires someone else to take their first step! 🌱✨ 💚 Let's celebrate the people behind the recipes, the connections behind the integrations, and the community behind Workato! 🔥 Who's ready to take the first challenge? Drop your video, tag your nominee, and let's get this movement started! 🎬🚀 #WorkatoCommunity #CommunityMonth #WorkatoRockstars #ShareYourJourney #LearnTogether #CommunityChallenge
Aaron W. Niyaz A. 💡 Idea: Workato Theme of the Month Hey everyone! 👋 I have an idea that could help us make our Workato community even more engaging and knowledge-driven. What if we dedicate each month to one specific Workato-related theme? 🚀 For example: * 🤝 Community Month — Share experiences, success stories, and community contributions. * 🍲 Recipe Month — Explore recipe design, best practices, and reusable patterns. * 🔌 Connector Month — Discuss custom connectors, SDK development, and connector use cases. * 🛡️ Security Month — Explore authentication, authorization, credential management, and security best practices. * ⚡ Performance Month — Share tips on task optimization, scalability, and efficient automation. * 🤖 Agentic AI Month — Explore Workato Agentic, Genie, and AI-powered automation. * 🏗️ Architecture Month — Discuss integration patterns, error handling, orchestration, and solution design. * 📊 Analytics & Observability Month — Explore monitoring, job reporting, dashboards, and troubleshooting. Throughout each month, we could encourage members to share practical use cases, tips and tricks, challenges, polls, mini quizzes, and lessons learned around the selected theme. The goal is to learn together, share real-world experiences, and strengthen the Workato community.
One thing I’m extremely proud of is optimizing a Service Appointment integration where I re-engineered the existing logic and reduced task consumption from approximately 18,000 tasks to just 8 tasks per run. This wasn’t just about reducing costs; it was about challenging the existing approach, identifying inefficiencies, and designing a more scalable and reliable solution without compromising business requirements. For me, the most rewarding part of engineering is turning complex problems into simpler, more efficient solutions. I believe true innovation is not always about building something new—it’s about making what already exists work significantly better and sharing that learning to help others grow.
I would generally recommend an event-driven approach over direct API calls for distributed cache environments because it decouples systems, scales better under load, and provides more resilient cache synchronization. For simpler integrations or cache invalidation use cases, REST APIs are often the most straightforward solution.
Here is my perspective No. APIs are the simplest and most common approach, but Workato can also integrate cache distribution through: Event-driven messaging ( Pub/Sub(previous name) event stream) Database synchronization Custom SDK connectors Webhooks Workato Datatables (for lightweight caching scenarios)
Lets connect tomorrow because I am not seeing this in my workspace
Hi dkuroda Good morning I hope you are doing well This happens because switching from polling to a real-time trigger changes how ServiceNow needs to authorize Workato. Real-time triggers work by creating a Business Rule record in the sys_script table — that Business Rule is what fires the webhook to Workato whenever a new incident is created. Your connected user needs explicit access control on that table for this to work, which polling never required. The exact permissions you need, per Workato's current docs: The account used for your ServiceNow connection must have a role with these access control rules: Table Type Operation Name BR record read sys_script / sys_script.* BR record write sys_script / sys_script.* BR record create sys_script BR record delete sys_script
