File received
Receive a JSON submission from your existing form backend at this Workflow's private webhook URL.
→
Ready-made Workflow
Send a webhook file to an ntfy topic
Connect ntfy, select a topic, and send a FastHook File in the webhook file field. Subscribers receive the attachment. Server file-size, storage, and daily message limits apply.
Use this templateCreates a new Draft · no credentials copied
What gets copied
The working graph, not another user's secrets
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Send ntfy file
Run the Send ntfy file action in ntfy.
Before activation
Connect your accounts in the Draft
Webhook
Send JSON submissions from your existing backend to the private webhook URL created in your Draft. No Webhook account is needed.
ntfy
Connect your own ntfy account and review the provider settings used by this Workflow.
Explore connected apps
Related Workflow templates
Webhook · ntfy
Send webhook alerts to ntfy
Connect ntfy and set a destination topic. Send message and title in the webhook JSON to deliver a high-priority notification.
- 1. Webhook · Alert received
- 2. ntfy · Send ntfy notification
Questions
Template FAQ
Does the template copy someone else's credentials?
No. FastHook creates a disconnected Draft. Connect your own ntfy accounts before activation.
Can I change the Steps and mappings?
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
What is copied into my workspace?
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
When does the Workflow start running?
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.