# Block sender API/Workflow?

**URL:** <https://community.hubspot.com/t/block-sender-api-workflow/113023>\
**Category:** APIs & Integrations\
**Tags:** workflows\
**Created:** [July 26, 2024, 10:11pm UTC](https://community.hubspot.com/t/block-sender-api-workflow/113023 "2024-07-26T22:11:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DanielCS](https://avatars.discourse-cdn.com/v4/letter/d/e36b37/32.png) [@DanielCS](https://community.hubspot.com/u/DanielCS)\
**Post date:** [July 26, 2024, 10:11pm UTC](https://community.hubspot.com/t/block-sender-api-workflow/113023/1 "2024-07-26T22:11:04Z")

</div>

Hello.

At job we have a workflow for spam that deletes a contact after 1 day if we set a custom property as spam.  
I managed to do an automation with Make/Integromat that gets an URL from a inbox message incoming from Facebook Messenger, checks it with Google API for potential unsafe images and if we get a not safe one it can set the custom property for spam to send it for that workflow.  
However, this won’t stop the user to comeback again, so we want to take this a step further and block the sender using the inbox action on hubspot. Is there a way to trigger this action using API or a Workflow? Couldn’t find a way to also automate this  
Thanks

---

<div class="post-metadata">

**Author:** ![KhushbooP11](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/khushboop11/32/8252_2.png) [@KhushbooP11](https://community.hubspot.com/u/KhushbooP11)\
**Post date:** [July 27, 2024, 10:18am UTC](https://community.hubspot.com/t/block-sender-api-workflow/113023/2 "2024-07-27T10:18:39Z")

</div>

Hi @DanielCS ,

If you want to automatically block a sender, you can use HubSpot’s API or automation workflows.

Here is what you can do -

1. Identify the user’s unique identifier from the message and check for unsafe content using your integration with Google’s API.

2. Next, if you find some unsafe content, just update a custom property in HubSpot to mark the contact as spam, which can trigger an automation workflow.

3. [HubSpot’s Conversations API](https://developers.hubspot.com/docs/api-reference/legacy/conversations/guide) can now update conversation threads in the Inbox and Help Desk, including their spam state, so you should use the current Conversations API rather than relying only on a custom contact property to represent spam.

Also want to add, that if direct blocking isn’t possible, consider using third-party tools like Zapier or Make.

Maybe you could also use HubSpot’s - Custom Code action in workflows, if available, to run code that interacts with the API for blocking.

I hope it helps!

_Moderator Note: this post was reviewed for relevancy and optimized for clarity on September 30, 2026. Thank you for your contributions to the HubSpot Community!_