Automatically Changing Ticket Requester based on Ticket Subject

Hi Oliver,

Why don't you use a trigger instead of an automation for that? The trigger could run when you receive a new ticket and if you are receiving the tickets from only one no-reply address you can specify it in the conditions. Something similar to this:
You can also add conditions for the ticket subject.

From here you can call the webhook that you have already created.

Ned

Thanks for the reply Ned,

I have two questions:

1. I find that when declaring the requester condition in the trigger, I can type in the no-reply email however it turns back to “-” when I click off/press enter.  It will only allow me to select from “assignee”, "current user"," and team members. We have reached our team member license limit. Is this intended?

2. With the Active Webhook,
I've declared:
Endpoint: https://ourorg.zendesk.com/api/v2/tickets.json
Method: PUT
JSON Body:
{
    "ticket":{
        "requester_id": 29553114917273
        }
}

I ran a test and found that the requester of the ticket hadn't changed despite the trigger applying. I checked the ‘Events' section and confirmed the ‘Message pushed to webhook.’ Do you have any theories as to why the requester didn't change?

It's scheduled last in the trigger order so I can confirm that no other conditions would interfere.

Edit: Turns out the Webhook 404'd due to ‘InvalidEndpoint.’ Looking into it.
Edit 2: Needed to be more specific with the endpoint. Changing it to https://org.zendesk.com/api/v2/tickets/{{ticket.id}} worked!

Hi Oliver,

Glad it worked out!

As for the email, I don't why, but ZenDesk doesn't allow to input a custom email and only agents can be selected.

Ned