Alert an intake channel
Post each new lead to the channel used by the office or sales team.
Notify your team in Slack when a new lead arrives
When Tinylawn creates a new lead, Zapier can use Slack’s Send Channel Message action to post the customer, request, property, timing, and source-record link you choose.
Via Zapier
One trigger. An automatic handoff.
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.
- 1
Tinylawn creates a lead
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.
- 2
Zapier maps the fields
Map the fields your chosen action accepts. Add filters for missing required values and test the resulting record before turning the Zap on.
- 3
Send a channel message
Choose a channel, write the notification format, and map in the Tinylawn lead fields your team needs for follow-up.
Lead context ready for the next step
- Customer name and contact details
- Service needs
- Property address
- Requested timing
- Lead source and Tinylawn link
Connection details
- Method
- Via Zapier
- Trigger
- New Lead
- Direction
- One-way from Tinylawn
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.
Workflows this connection fits
Surface urgent context
Include the request, address, timing, and caller details in one message.
Link back to the source
Give the team a direct route to the complete lead in Tinylawn.
Common questions about this connection
How does Tinylawn connect to Slack?
This guide covers the Zapier workflow: Tinylawn’s New Lead trigger sends captured details to Slack through its supported Zapier actions. You need accounts for both apps and Zapier. This workflow sends data one way from Tinylawn.
What starts the workflow?
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.
Do later changes sync, and can I replay a 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.
What Tinylawn data can I map?
Available fields include Customer name and contact details, Service needs, Property address, Requested timing, Lead source and Tinylawn link. Empty values remain empty, and the destination action determines which fields it accepts.
