Contact Tag Sync Operator
Listens for inbound webhooks carrying a contact identifier and a tag name, resolves the contact in your CRM, ensures the tag exists (creating it on demand), applies it, deduplicates against recent syncs in a rolling 24-hour window, and writes an audit row so every change is reviewable. Emails an alert when a sync fails so nothing is silently dropped.
Agent snapshot
Built for cross industry work, not a generic template.
0
runs observed
0
community clones
3
integrations used
2
labels matched
Sample input
Build an agent to contact Tag Sync Operator. Use Telegram, HubSpot, and Google Sheets. Focus on operations. Return a ready-to-review result after each run.
Sample output
Whenever your messaging tool fires a webhook with a contact email and tag, finds the contact in HubSpot, creates the tag if it's missing, applies it, and logs every action to a sheet and the agent database.
What this agent automates
This run includes 8 concrete steps from the published agent data.
Receive webhook payload and parse contact identifier + tag name
Check the dedupe window in the agent database; skip and log if this contact+tag was already synced recently
Normalize the tag name using the configured naming convention
Look up the contact in the CRM by the chosen match field (email, phone, or either)
If contact missing, apply the missing-contact policy (create, skip-and-log, or queue for review)
Ensure the tag exists in the CRM; create it if the tag-creation policy allows
Integrations used
Contact Tag Sync Operator connects Telegram, HubSpot, and Google Sheets.
Telegram
Connected in this agent
HubSpot
Connected in this agent
Google Sheets
Connected in this agent
Clone Contact Tag Sync Operator
Start from the exact agent behind this page, then adapt the prompt, apps, and review steps to your cross industry workflow.
Plans start at €20/mo