Streamline Data Cleanup with DELETE Method in Webhook Blocks

DELETE Method in Webhook Block

Do you need to remove a support ticket, delete a user, or clean up records in another system? The DELETE method in the Webhook block helps you do just that from within your bot flow. It allows you to directly remove data from external platforms like Zoho Desk, CRMs, or any service that supports APIs.

Whether you’re helping a user cancel a request, unsubscribe from a service, or clean up test data, DELETE lets you automate the removal process quickly and securely.

Learn more about webhooks: Introduction to Webhook Block in GC 
​

What is the DELETE Method? 

The DELETE method is used to permanently remove an existing record from an external system using its API. It’s like telling the system, “This item is no longer needed; please remove it.”

This method is direct and final; it tells the system to erase that specific item using its unique ID or endpoint.
 

When should you use it? 

Use the DELETE method when:
  1. A user wants to cancel a support request.
  2. You need to clean up old, duplicate, or test data.
  3. Someone asks to be removed from your system.
  4. A subscription or service has ended and should be deleted.
Use DELETE when the user initiates a clear remove or cancel action or when your process calls for automatic clean-up.
Example Use Case
Let’s say your bot helps users manage their support tickets, and one user decides they no longer need help with a particular issue. Here’s how you can use the DELETE method:
 
DELETE URL:
https://api.yourapp.com/delete-ticket/TX12345 (Where TX12345 is the ID of the ticket to be deleted.
 
Sample Response:
 
{ 
  “ticket_id”: “TX12345”, 
  “status”: “Deleted” 
 } 

Your bot can then show this confirmation message:
“Your ticket TX12345 has been successfully deleted. Let us know if you need help with anything else.”

Body (Optional) 

Usually, no request body is needed with DELETE. However, some APIs may require details such as authentication or a reason for deletion. Always check the API documentation to be sure. 

Benefits of using the DELETE Method 

  1. Keeps your systems tidy by removing unwanted records.
  2. Gives users control over their data; great for privacy and compliance.
  3. Prevents clutter in external systems by aligning data with real user intent.
 

Understanding the differences between Webhook HTTP Methods 

GET
POST
PUT
PATCH
DELETE
GET
Primary Purpose
Typical Use Cases
Request Body
Example Scenario
Retrieve data from a server
- Fetch user details
- Get ticket history
- Retrieve knowledge base articles
No
Display a user’s subscription status based on their email.
POST
Primary Purpose
Typical Use Cases
Request Body
Example Scenario
Submit data to create a new resource
- Create a support ticket
- Submit a form
- Log user feedback
Yes (e.g., JSON)
Create a new ticket in Zoho Desk with user information.
PUT
Primary Purpose
Typical Use Cases
Request Body
Example Scenario
Update or replace an existing resource
- Update ticket status
- Modify user contact details
- Change subscription plan
Yes (full resource)
Change the priority of a support ticket to “Urgent”
PATCH
Primary Purpose
Typical Use Cases
Request Body
Example Scenario
Apply partial modifications to a resource
- Update ticket priority
- Change the user’s phone number
- Modify specific fields
Yes (particular data)
Update only the status field of a ticket to “In Progress”
DELETE

Primary Purpose

Typical Use Cases​

Request Body

Example Scenario

Remove a resource from the server

- Delete a support ticket

- Unsubscribe a user
- Remove a customer record

Optional

Delete a user’s support ticket upon request

Learn about GET, POST, PUT and PATCH

FAQs 

Can I undo a DELETE action?
Usually not. Once deleted, the data is often gone for good unless the API supports soft deletes or trash bins. Be cautious.
Can I delete tickets in Zoho Desk with this action?
Yes, if the Zoho Desk API supports it and you have the ticket ID, you can use DELETE to remove it.
Do I need a request body for DELETE?
Sometimes. Some APIs require a body, others don’t. Check the API documentation carefully.

Tips

  1. Always test DELETE actions in a safe (sandbox) environment first.
  2. Add a confirmation message or step in your bot before triggering deletion.
  3. Check API docs carefully for what’s required, especially around authentication and body structure.
  4. Clearly inform users what’s being deleted and confirm their consent.
  5. Use DELETE only when you’re sure the record should be permanently removed.

Learn more about webhooks: Introduction to Webhook Block in GC