Workflow overview
Why this workflow matters
Helpful for business development and pipeline building. Relevant for managed services and support workflows.
> ⚠️ Self-hosted only — This template uses a community node (AlekSystem-nodes-tallyforms) and cannot run on AlekSystem Cloud. Who it's for This workflow is for support, operations, or customer success teams that use Tally for intake forms and HubSpot as their CRM. It automates ticket creation so no submission is lost and every ticket is linked to the right contact. How it works A Tally form submission triggers the workflow via webhook. HubSpot is searched for an existing contact matching the submitted email address. An If condition checks whether a matching contact was found. If no contact exists, a new HubSpot contact is created or updated with the submitted details. Contact ID, first name, and last name are normalized from whichever branch was taken. A new HubSpot support ticket is created and associated with the resolved contact. How to set up [ ] Install the AlekSystem-nodes-tallyforms community node on your self-hosted AlekSystem instance. [ ] Connect your Tally account and set the correct form ID in the Tally trigger node. [ ] Connect your HubSpot account (app token or OAuth) to the Search, Upsert, and Create Ticket nodes. [ ] Map Tally form fields (email, first name, last name) to HubSpot contact properties in the Upsert node. [ ] Configure ticket properties (pipeline, stage, subject) in the Create HubSpot Ticket node to match your HubSpot setup. Requirements Self-hosted AlekSystem instance AlekSystem-nodes-tallyforms community node Tally account with a published form HubSpot account with API access (app token or OAuth) How to customize Extend the Set node to pass additional Tally fields (e.g., message body, phone number) into the ticket description or custom properties. Add a follow-up step after ticket creation to send a confirmation email to the submitter via Gmail or SendGrid. Replace the Tally trigger with another form tool (e.g., Typeform or Jotform) by swapping the trigger node and remapping the field references.
Best fit
Categories
Services
Use cases
Need another direction?