Create the contact
Match a caller to an existing HubSpot contact or create a new one.
Use HubSpot’s Find or Create Contact action with a nonempty search property and value. Review the matching rule with your own contacts, then choose whether to create a contact when none is found.
Via Zapier
Tinylawn remains the intake layer. Zapier moves selected lead data into the action you configure; your destination tool remains where the team manages the work.
When a call or intake flow creates a lead, the New Lead trigger starts your enabled Zap with the captured details. It does not wait for your team to approve the lead.
Map the fields your chosen action accepts. Add filters for missing required values and test the resulting record before turning the Zap on.
Choose a contact property to search, such as email, and filter out leads missing that value. Enable create-if-missing if needed and map the contact fields your action offers. A found contact is not updated by this step; use a separate supported action if you need to record each inquiry.
Requires a Zapier account, a Tinylawn organization API key, and access to the destination account. Destination action availability can depend on that provider’s plan.
Match a caller to an existing HubSpot contact or create a new one.
Add a supported engagement or note action if your team needs a record of every inquiry.
Continue into the supported HubSpot actions you choose in Zapier.
This guide covers the Zapier workflow: Tinylawn’s New Lead trigger sends captured details to HubSpot through its supported Zapier actions. You need accounts for both apps and Zapier. This workflow sends data one way from Tinylawn.
New Lead is the only Tinylawn trigger. An enabled Zap starts automatically when a lead is created, without a Tinylawn approval step. Your team still confirms requested service and timing. Changes to an existing lead do not trigger another run.
This workflow sends data one way when a lead is created. Later edits in either app do not sync through New Lead. Before replaying a run or enabling a second Zap, check for records already created: a create action can produce duplicates. Find-or-create steps only match by the rules you configure.
Available fields include A nonempty contact search property and value, Customer name and contact fields offered by the action. Empty values remain empty, and the destination action determines which fields it accepts.