Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Workato recipe inventory and stopped-recipe events. Import recipe inventory and create events for stopped recipes with explicit failure causes. Current availability: Read intake implemented; provider acceptance required.

Before you start. Workato API entitlement, a company API client token and its actual hosting region.

Step 1. Open Company > Security > Workato. Select the region matching the account and enter its API token.

Step 2. Configure severity, automatic tickets and the company notification mailbox as needed. Save, verify read access and enable sync.

Step 3. Sync reads paginated recipes while excluding recipe code. A stopped recipe with a recorded failure cause produces a stable automation event. Successful or manually stopped recipes are not all treated as incidents.

Step 4. Inspect inventory, event and linked ticket, then pause the connection to stop further polling.

Now verify the result. An approved known failed recipe appears once and maps to the correct company. Repeated polling does not duplicate the linked event.

If you get stuck. This adapter does not start/stop recipes, run jobs or publish Workato changes. Confirm API entitlement, token scope and region when access is rejected.

Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.