Before
A team member likely had to receive the update data, authenticate or switch into Salesforce, prepare the records for upload, and divide larger updates into batches. They also had to monitor batch states, confirm completion, and manually communicate the outcome in Slack.
How it works
- Receive the bulk update data through the emailhook and prepare it by dividing the records into processable chunks.
- Authenticate with Salesforce, create an Asset update job, process each chunk sequentially, and monitor queued and in-progress states with scheduled checks.
- Wait for all batches to finish, mark the job as UploadComplete, and send the resulting status message to a Slack channel.
Workflow details
- Data intake: The workflow starts when an emailhook receives the data and parameters for a bulk update. It prepares the incoming information for processing and separates the data into manageable chunks.
- Salesforce authentication: The automation obtains a Salesforce login session before creating an ingest job configured to update Asset records.
- Batch processing: Each data chunk is processed sequentially through the ingest job. The workflow waits between checks and evaluates whether the job is queued, in progress, or ready to move forward.
- Completion control: After all batches have been processed, the workflow waits for the batch activity to settle and updates the ingest job state to UploadComplete.
- Status communication: The automation extracts the relevant message components, builds Slack message blocks, and posts the resulting status message to a channel so the outcome is communicated without a separate manual handoff.
What changed
Bulk Asset updates now move from emailhook intake to Salesforce batch processing without repeated manual uploads or status checks. Completion handling and the Slack notification are performed automatically after the workflow has processed the batches.
Work removed
Receiving and preparing update data, dividing records into batches, checking queued or in-progress job states, waiting for batch completion, marking the ingest job complete, composing the status message, and posting the update to Slack.
Expected outcome
A conservative expectation is that each run removes multiple manual batch-status checks and one completion-notification handoff, with automated polling at 10-second intervals and a 30-second final wait; actual savings depend on batch size and processing time.
