EdgeStar Support

Winston - You are correct - but that is where the HTTP Target comes into play.  As long as you can establish the correct conditions for the trigger to run on the ticket where you would like the organization to be set for that requester - then the HTTP Target and JSON code I pasted above will set the Organization.  In our instance of ZenDesk, The below trigger was something I tested successfully yesterday - the conditions are very simple for my test - just needs to contain a specific tag, so you would want to determine the right set of conditions in your use case.  But...once the condition is met - that JSON code will update the organization for that ticket requester. 

You can use an HTTP target to accomplish this provided you can set the condition properly to fire a trigger.  I assume that based on brand / form or other requester level attribute etc you can set a tag that can be used for the correct condition to fire the trigger. 

If you have an existing HTTP Target for .../api/v2/users/{{ticket.requester.id}}.json then you can simply call that, otherwise you will want to create a new one by going to Extensions / Add Target / HTTP target

Name: whatever you want to call it, i.e. "Update Requester"

Url: https://your-zendesk-domain.com/api/v2/users/{{ticket.requester.id}}.json

Method = Put

Content Type = JSON

Choose your authentication type for the API call and create

Next, find the organization id.  Simply go to People / Organizations and click the one you want - get the ID that is in the url, i.e. https://your-zendesk-domain.com/agent/organizations/123456789/tickets

Next, create a new trigger for updating the organization field - set the correct conditions, i.e. ticket created and tag must contain xyz etc etc.  Add the action to Notify Target - and select the appropriate target that you just created (i.e. Update Requester).  Use the below JSON body - just update the value to be the organization id you found in the above step in place of what I have listed below. 

{
"user":{
"organization_id" : 123456789
}
}

NOTE: You must be sure to have a condition that will only be met once.  As an example, one of the ALL conditions might be that Tags | Contains None of the Following | org_updated (as an example).  Then just add an action so that the trigger adds that tag after it executes the JSON. With the tag now added to that ticket the Trigger will not fire again.

Graeme - Thank you!!!  Worked like a charm.  I really appreciate the help.

Hi - I am wondering if anyone can help with JSON for a future date.  Specifically, I am less concerned about when the last satisfaction was sent and more interested in when the next satisfaction might be sent. I was hoping that the JSON referenced above could be  'now' + 30 days but I am unsure how to alter the JSON body correctly.  Any ideas?  Thanks!