# Policy Workflow Step 6

Next, we want to add another step to our policy action. To do this we again go back to the Policy Action itself by clicking on the “init\_installer\_steps” Policy Action icon on the left.

Again we need a Send step since we need to send the updated approval document as a W3C Verifiable Credential from the Guardian to Hedera for further processing. To do this we again click on the “Send” icon in the top navigation bar to add another Policy Action step.

We now proceed in the same way as with the “Send” step from “save\_new\_approve\_document” to configure this policy action step.

Note that the data type must be “Hedera” since the document is to be sent as a verifiable credential for permanent storage to Hedera.

![](/files/Ngk7VJXNvze0juYs2k5X)

**Programmatically this workflow step looks like this:**

```
    // Now send the document to Hedera Topic.
    {
      "tag": "send_installer_vc_to_hedera",
      "blockType": "sendToGuardianBlock",
      "dataType": "hedera",
      "entityType": "Installer",
      "uiMetaData": {}
    },
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guardian.hedera.com/guardian-dev/guardian/standard-registry/policies/policy-creation/creating-a-policy-through-policy-configurator/policy-workflow-step-6.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
