Support destinations with encrypted secret inputs in schema
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
We don't support secret (encrypted) inputs in workflows yet so we filter out those destinations in the dispatch list
This means some high value destinations like Meta ads are not yet usable in Workflows.
To support this, the main thing we are lacking is an encrypted_inputs field on workflows that is hashed+salted on save just like with realtime destinations (posthog_hogfunction table in PG)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining how realtime destinations use the posthog_hogfunction table in PostgreSQL, then trace where workflow destinations are filtered from the dispatch list. Identify the workflow schema and persistence paths involved. Done means encrypted_inputs are stored hashed and salted on save, and destinations requiring secret inputs are no longer filtered out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- backend, databases, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100