| I'm going to add the workflow to Contentful. I'm just going to document the one I'm submitting to the creator library, which is one away from the threshold for monetization. And then that can be just to prove it's got the code sample. We can actually do code samples from the JSON and to test out the main code block and specific areas and make sure I'll make sure as well the JSON is a type of supported language in the syntax highlighting, and that will validate that it's working. | |
| It might just be more efficient to say that what's been, forget the importing the old posts. Or I can just gradually update them going forward. And I wanna create a tag as well for N8N workflows. And then so that I can update this link from the agent website that I'm building. | |
| And I might ask N8N. I read the guidelines now for the workflows if they might would mind sharing for credential sanitization, redacting things beyond API keys. If you have, for example, your name in an agent configuration or an email, I'm manually editing them. And then emails, what is their preference regarding that? Is it okay to use things like redacted placeholders or dummy emails? What's their preference for how to submit them? | |
| And of course, it's important as well to check the workflows before submitting them because the API keys shouldn't be exposed because they'd be linked to its credentials. We just want to make sure that there's nothing else that, for example, in the payloads and webhooks, if those might reveal any IDs or anything else. At the moment, they're worth manually inspecting. |