Landbot + Zendesk

Create Zendesk tickets from new Landbot activated blocks

Streamline your customer support process with this automation between Landbot and Zendesk. Whenever a new block is activated in Landbot, a ticket will be created in Zendesk, helping your support team stay on top of incoming issues and ensuring a swift resolution for your users. Save time and improve efficiency with this seamless workflow.

When this happens...
Zapier Block Activated
Triggers when a visitor reaches the "Zapier Integration" Block within a Landbot.
TriggerInstant
automatically do this!
Create Ticket
Triggers when a new ticket is added (Zendesk may take an hour to make tickets available via their API with this trigger).
ActionWrite

Start free with email

Start free with Google

Start free with email

Start free with Google

Free forever for core features
14 day trial for premium features & apps

Supported triggers and actions

- BotRequired
- Blocks
Trigger
Instant
Try It
- ViewRequired
Trigger
Scheduled
Try It
- Tags
Trigger
Instant
Try It
- Ticket (Required for non-admins)
Trigger
Scheduled
Try It
New User
Triggers when a new user is created.
Trigger
Scheduled
Try It

- UserRequired
- user_delete_copy
- Permanent Deletion
- user_delete_test_copy
Action
Write
- TicketRequired
- TagsRequired
Action
Write

- TicketRequired
- CommentRequired
- Should the comment be public?
- FileRequired
Action
Write
- TicketRequired
- TagsRequired
Action
Write
- TicketRequired
- Subject
- Assignee
- Group
- New status
- New Comment to add to the Ticket
- New Comment format
- Should the new Comment be public?
- Tags
- Additional Tags
- Remove Tags
- Type
- Priority
- Submitter
- Brand
- External ID
- Requester
- Sharing Agreements
- Ticket form
- Collaborators
- Collaborator Emails
- Email CC
- Attachment
Action
Write
- NameRequired
- Email
- Details
- Notes
- Phone
- Tags
- Role
- Organization
- External Id
- Verified
Action
Write
- QueryRequired
Action
Search
- QueryRequired
Action
Search
- QueryRequired
Action
Search
- Info
- Type
- SubjectRequired
- Assignee
- Collaborators
- Collaborator Emails
- Group
- Requester Name
- Requester Email
- First Comment/Description format
- First Comment/DescriptionRequired
- Should the first Comment be public?
- Tags
- Status
- Priority
- Submitter
- Ticket form
- Sharing Agreements
- Brand
- External ID
- Email CC
- Attachment
Action
Search or write
- QueryRequired
- NameRequired
- Email
- Details
- Notes
- Phone
- Tags
- Role
- Organization
- External Id
- Verified
Action
Search or write

New Group
Triggers when a new group is created.
Trigger
Scheduled
Try It
- Organization
Trigger
Scheduled
Try It
New Organization
Triggers when a new organization is created.
Trigger
Scheduled
Try It
- Organization
Trigger
Scheduled
Try It
New View
Triggers when a new view is created.
Trigger
Scheduled
Try It
- NameRequired
- Details
- Notes
- Tags
- Domain Names
- External Id
- Group Id
- Shared Tickets
- Shared Comments
Action
Write
- SubjectRequired
- Assignee
- Collaborators
- Collaborator Emails
- Group
- Requester Name
- Requester Email
- First Comment/Description format
- First Comment/DescriptionRequired
- Should the first Comment be public?
- Tags
- Status
- Type
- Priority
- Submitter
- Ticket form
- Sharing Agreements
- Brand
- External ID
- Email CC
- Attachment
Action
Write
- TicketRequired
- Comment body
- Comment format
- Should the Comment be public?
Action
Write
- OrganizationRequired
- Name
- Details
- Notes
- Tags
- Domain Names
- External Id
- Shared Tickets
- Shared Comments
Action
Write
- UserRequired
- Name
- Email
- Details
- Notes
- Phone
- Tags
- Role
- Organization
- External Id
- Verified
Action
Write
- HTTP MethodRequired
- URLRequired
- Query String Parameters
- Headers
- Additional Request Headers
- Body
Action
Write
- Info
- Type
Action
Search
- Ticket IdRequired
Action
Search
- QueryRequired
Action
Search
- QueryRequired
- NameRequired
- Details
- Notes
- Tags
- Domain Names
- External Id
- Group Id
- Shared Tickets
- Shared Comments
Action
Search or write