Integration
Let a confirmed click start your own automation.
A customer presses the button in your email and confirms. Responello sends the event to an HTTPS endpoint you control. Your pipeline, workflow tool or script does the rest.
Design the receiving workflow
Use the event as a prompt for your own automation, queue, CRM bridge, or internal routing. One example: a design studio connects the button in its hand-over email to its deployment automation, and the client's confirmation publishes the finished website. Keep the receiver fast and return a successful HTTP response.
- Use a public HTTPS endpoint.
- Validate the shared secret configured for the channel.
- Make processing idempotent so retries do not create duplicate work.
Test failure behaviour
Responello records delivery outcomes and marks repeatedly failing channels as unhealthy. Your workflow should also log rejected or malformed requests without storing more data than needed.
- Test the endpoint before assigning production buttons.
- Rotate the secret if it may have been exposed.
- Monitor the receiving service and review Responello delivery analytics.
Practical notes
Responello sends the webhook. Publishing, deploying or any further step happens in your own automation.
Private network and unsafe destination addresses are blocked.
Do not place credentials directly in the endpoint URL.
Your receiving system is responsible for its own access controls, retention, and downstream processing.
Put a button where the moment matters.
Create a button, choose where the signal should arrive, and test the complete confirmation flow.