Turn CompanyCam service tags into Salesforce cases and Slack alerts

Whenever a photo in CompanyCam gets tagged with something that signals a service issue (tags like warranty, callback, punch list, or damage found), fire this workflow to open a Salesforce case and ping the service team in Slack so a field manager can respond right away.

The trigger is a CompanyCam webhook subscribed to the photo.tag_added event. First, inspect the added tag and only continue if it matches the configured service-alert tag list. Treat that list as a customization knob; default it to warranty, callback, punch list, damage found. If the tag is not on the list, exit quietly without creating anything.

For each qualifying event, run the following steps:

• Call CompanyCam Retrieve Photo to get the image URL and description for the tagged photo.

• Call CompanyCam Retrieve Project on the photo's project to pull the jobsite address and the homeowner or primary contact.

• Call CompanyCam List Photo Comments to gather any crew notes attached to the photo.

• Run a Salesforce SOQL Query on the Account object to find the account that matches the project address or the homeowner name. If multiple candidates come back, pick the closest by address and keep the second-best in mind for the Slack note.

• Before creating anything, run a second Salesforce SOQL Query on Case filtered by a stable reference to the CompanyCam photo id (for example a custom field or a token embedded in the case subject or description). If a case already exists for that photo, skip the create step and just refresh the Slack thread if one is already there.

• Call Salesforce Create Case with a subject naming the tag and address, a description drafted from the photo description plus the crew comments, the matched Account (leave blank when no confident match), and a priority derived from the tag (damage and warranty escalate; punch list stays normal).

• Call Slack Send a Message to the service team channel with the photo image or URL, the project address, the tag that fired, a one-line summary, and a deep link to the newly created Salesforce case.

Reasoning guidance for the agent: decide which tag values should escalate versus be ignored based on the configured list; anything not on it is a no-op. Draft the case summary in the crew's voice, for example 'Warranty callback flagged on the roof at 123 Elm St. Crew note: seam popped after the last storm.' If Retrieve Project comes back without an owner or address, still open the case and call out the missing info in Slack so the field manager can fill it in. Never open a duplicate case for the same photo id, even if multiple alert tags fire on the same photo.