What it's forFeed StrataWorx events and nightly data into your own cloud tools.
Who it's forAdministrators and your IT team.
Step by step
- Step 1: SAP BTP Event MeshCreate an Event Mesh service key and enter its messaging REST URL, token URL, client ID and secret. Choose a topic prefix in your namespace. StrataWorx publishes to <prefix>/job/created, <prefix>/job/updated and <prefix>/message/received as CloudEvents.
- Step 2: SAP BTP Integration SuiteDeploy an iFlow with an HTTPS sender, create a Process Integration Runtime service key (plan integration-flow) and enter the iFlow URL and key. Route events on to S/4HANA, SuccessFactors or any system, including on-premise ones through Cloud Connector.
- Step 3: AWSCreate an IAM user (or role credentials) with only events:PutEvents, sqs:SendMessage or s3:PutObject. Choose EventBridge to trigger Lambda and Step Functions, SQS for your own workers, or S3 for a nightly data export. Use region ap-southeast-2 for Sydney.
- Step 4: Microsoft AzureEvent Grid: enter the topic endpoint and access key. Service Bus: create a shared access policy with Send only. Blob Storage or Data Lake: create a container SAS URL with Write and Create (add Read to also import from it).
- Step 5: Google CloudCreate a service account with Pub/Sub Publisher (for events) or Storage Object Creator (for exports), download a JSON key and paste it in. BigQuery can read the nightly files directly.
- Step 6: Nightly exportsS3, Blob Storage and Cloud Storage receive one JSON Lines file per dataset per day (lotline/jobs/2026-10-15.jsonl) plus latest.jsonl. Press 'Load data now' to test.
Tips
- Events are CloudEvents 1.0 with type au.lotline.job.created and so on, so any cloud tool that understands CloudEvents can read them.
- Work orders that came in from another system aren't sent back to business systems, only to chat and event buses, so nothing loops.
Previous and next follow the Connections section.