New Bug Encountered:Google Docs not opening from Workflow Body Template

[Daisy_Ramirez]

[quote=“Daisy_Ramirez, post:20, topic:10034, full:true”]
Hi Levent, would you know how to trigger a second webhook from the first? See notes to Phil on this question.
"Just an update it looks like the second webhook is not triggering as there’s no activity in the audit logs. I created an action to update a field called Copy and set it to TRUE. I was hoping the Update would have triggered the second webhook but not sure if it recognizes the field update as a workflow “update” if it was not a manual one.

Will standby. Thanks Levent

[LeventK (Levent Kulacoglu)]

@Daisy_Ramirez
I’m afraid a data change with workflow cannot trigger a second webhook unless you are not doing it with API. Only if you use API to change the data, it will trigger the actions and workflows associated with that table. But of course @Phil can explain better.

[Phil (Philip Garrett)]

Are you expecting a workflow DataChange action to trigger a webhook workflow rule?
If so, that will not work because workflow DataChanges never trigger any form of workflow rule.

[Daisy_Ramirez]

Yes, ok what if I change the data of the 2nd table (child) from the 1st table (parent) in Parent/Child type of form - will this get it to trigger?

[Daisy_Ramirez]

Hi Levent, so I could first run an Edit webhook but how would I run the edit on the 2nd table (child)?

[Daisy_Ramirez]

Will an action data change trigger the workflow webhooks?

[Phil (Philip Garrett)]

I am not sure I understand the big picture, but here are the rules:

A Workflow can be triggered by:

1. Any change made by the client.The client change can occur because of a user enter value or an action performed on the client.
2. A change made by the REST API.

A workflow cannot be triggered by:

1. A DataChange invoked by a workflow rule. (We do not do this because were worried that this might lead to infinite recursion. One DataChange might make a change that triggers another workflow rule. That workflow rule might make a DataChange that triggers yet another workflow rule. If the user is not careful this can result in loops where: A triggers B, which triggers C, which triggers A, which triggers B, which triggers C, and so forth in an infinite loop.)

A single workflow rule can invoke a sequence of workflow actions.
These actions can include a sequence of webhook calls that invoke the REST API.
Not sure if that will help in your case.