Yes, the

parse: true

configuration in the webhook should work with the settings flow. This configuration allows the webhook to parse the response and potentially modify the identity. However, modifying the identity is currently only possible during the registration and settings flows. Here is an example of how you can configure the webhook to parse the response:

yaml hook: web_hook   config:     response:       parse: true

When the webhook target returns a 200 OK response code and the response body is a JSON object with the key

identity

in it, the values from that object will be used to change the identity before it is saved to the database. If your endpoint is not receiving the webhook, there might be an issue with the setup of your webhook or the flow. Make sure that your webhook is correctly configured and that it is correctly integrated into the settings flow. For more information, you can refer to the [Ory documentation on integrating with external systems through webhooks](https://www.ory.sh/docs/guides/integrate-with-ory-cloud-through-webhooks#modify-identities).

Yes, setting

parse: false

in the webhook configuration should also work correctly. This configuration means that the webhook response will not be parsed and interpreted. Here is an example of how you can configure the webhook with `parse: false`:

yaml hook: web_hook   config:     response:       parse: false

When

parse: false

, the webhook's logic is called after the system creates a new identity. This is different from when

parse: true

, where the logic is called before the system creates a new identity. For more information, you can refer to the [Ory documentation on integrating with external systems through webhooks](https://www.ory.sh/docs/guides/integrate-with-ory-cloud-through-webhooks#flow-interrupting-webhooks).