A finished task. A connected workflow.
Learn how to send a completed result, choose automatic delivery, and handle uncertain handoffs.
Prepare the receiving workflow.
Choose n8n, Make, Zapier, or a custom webhook. Create a receiver that accepts JSON POST requests through a public HTTPS URL.
Begin with a receiver that lets you inspect the data before sending messages or changing other applications.
Add a destination.
In WebAct, open More → Integrations to reach the account website. Add a connection, choose the platform, give it a recognizable name, and paste its URL.
Pro supports 3 destinations. Business supports 25. Platform subscriptions and permissions are separate from your WebAct plan.
Send one result manually.
Complete and verify a task in WebAct. Select that result and a destination in the integration screen, then send it. Inspect the receiving workflow’s execution before mapping follow-up actions.
The payload includes the instruction, summary, source-page URL, and verification explanation. It excludes screenshots and file attachments.
Choose automatic delivery only when ready.
Business can opt into automatic delivery for a destination. It applies to future completed results after the connection is created. Confirm that you want those result details shared with the destination.
Review the connected workflow whenever its downstream actions change. A useful prototype and an unattended workflow can have different consequences.
Treat uncertain delivery carefully.
If delivery is interrupted, check the receiver before retrying. An accepted request may have reached it even if WebAct did not receive the acknowledgement. Receiving workflows should deduplicate the stable delivery ID.
Removing a destination cancels queued work. It does not erase data or undo actions already accepted by another service.