AlfaDocs and Gleap Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep AlfaDocs and Gleap matched by integrating their events and actions. When support events happen in AlfaDocs, update the Gleap automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about AlfaDocs and Gleap

Detailed info you need to know about AlfaDocs and Gleap integrations in WEXTL. Explore which modules apps support and how you connect them.

  • AlfaDocs

    • Support
    • 2 triggers
    • 8 searches
    • 6 actions

    Practice management for dental clinics, with patients, appointments and records.[5]

  • Gleap

    • Support
    • 2 triggers
    • 67 searches
    • 81 actions

    Customer feedback and support platform with tickets, contacts, help center articles and surveys.[6]

How to connect AlfaDocs to Gleap

Set up your AlfaDocs and Gleap integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between AlfaDocs and Gleap work in WEXTL?

WEXTL exposes actions and triggers for AlfaDocs and Gleap that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

AlfaDocs triggersGleap actions

AlfaDocs modules

  • Create a Patient Registers a patient in a practice archive from a First Name and Last Name. Add Email, Date of Birth, Italian Fiscal Code or a Price List ID, and Custom Fields for extra data.
  • Create an Appointment Books an appointment in the practice agenda and colors it with a Color ID. Use Duration, Chair ID and Operator ID to place it, and All Day Appointment for a full-day booking.
  • Delete a Patient Removes a patient from the archive of a practice.
  • Get a Care Plan Looks up one care plan by Care Plan ID. The result shows its State and Date accepted, along with the Branch and the Operator ID of the person responsible.
  • Get a Patient Loads one patient by Patient ID, with name, Email, Phone Numbers, address and Gender.
  • Get an Appointment Fetches a single appointment of a practice by its Appointment ID. The result has its Date, Patient ID, State, Duration, Chair ID and Color ID.
  • Make an API Call Makes an authorized free-form request to the AlfaDocs REST API with your saved credential.
  • Search Appointment Care Plan Entries Lists the entries attached to one appointment, each as its own bundle with Entry ID, Price, Discounted price, Done and Date done. Use Limit to restrict the count.
  • Search Appointments Finds appointments in a practice archive. Filter by Start Date, End Date, Appointment State or Patient ID, and add a Limit to shorten long result lists.
  • Search Custom Object Fields Lists the custom fields defined on objects in a practice archive, each with its Label, Technical Name, Type and Choices. Use Object Type to look at one kind of object.
  • Search Free Time Slots Looks for open slots on the practice agenda from a Start Date, each as long as the Duration in minutes. Use Operator IDs to look at selected operators only, and End Date to extend the search.
  • Search Patients Finds patients by Phone Number together with its Phone Number Prefix, or by Italian Fiscal Code. Each match is a separate bundle. Set a Limit for fewer matches.
  • Update a Patient Edits a patient found by Patient ID. Change the name, Email, Street Address, Province or Source ID, turn Email Enabled on or off, or add entries to Custom Fields.
  • Update an Appointment Edits an existing appointment by its Appointment ID. Change the date, Duration, Appointment State, Chair ID or Color ID, or attach it to another patient.
  • Watch Appointments Polls a practice archive on a schedule and runs a workflow per new appointment. Cap each execution with Limit.
  • Watch Patients Checks the patients on file at each interval and runs the workflow for new ones. Use Limit to set how many patients one run takes.

Gleap modules

  • Add a Company Member Links a contact to a company in Gleap. Turn on Move Tickets to carry the open tickets of the contact over to the company.
  • Add a Contact Memory Stores a named note on a contact for later conversations, with a Name and the Content to remember. Use Description for a summary of up to 240 characters.
  • Add AI Content Saves a knowledge entry that the Gleap AI can answer from, with a Title, Content and Type. An existing entry with the same Content ID is replaced. Add a link to it with Read More URL and Read More Label.
  • Add to a Pipeline Places a record on a pipeline board by its Record ID. Use Stage ID to start it in a given stage and Field Values to fill its properties.
  • Archive a Ticket Archives a ticket, so List Tickets hides it unless Include Archived is on.
  • Close a Ticket as Spam Closes a ticket and flags it as spam, so List Tickets hides it while Spam stays empty.
  • Count Companies Counts the companies stored in your Gleap project and returns a single Count.
  • Create a Help Center Article Writes a new article inside a help center collection. Fill Content or Plain Text for the body and set a Slug and Tags if you need them. Turn off Draft to publish it right away.
  • Create a Help Center Collection Creates a collection that organizes help articles. Use Parent Collection to nest it, External ID for your own reference and Site to place it on a help center site.
  • Create a Message Posts a message on a ticket as Message text or as a Markdown Message. Turn on Internal Note for a note only the team sees, and Send to Channel to also deliver it by the ticket channel such as email.
  • Create a Message Template Saves a reusable reply with a Title and Content. Turn on Public so everyone in the project can use it, and add Tags to label it.
  • Create a News Item Adds an in-app news item with a Subject and an optional Message. A Status of Live publishes it right away.
  • Create a Team Builds a team of support Members with an Assignment Method that says how tickets are distributed. Turn on Only Online Members to skip people who are away.
  • Create a Ticket Opens a ticket of a chosen Ticket Type. Set Title, Description, Priority and Status, link a Contact ID, and route it with Assigned To or Team.
  • Create a Ticket Type Defines a new board for tickets. Set Visible to Members and Visible to Teams to restrict who sees it, or leave both empty to share it with everyone.
  • Create a Ticket with a Message Opens a ticket and posts its first Message in one step. Use Email to reach a customer without a contact, and turn on Prevent Auto Reply to stop the automatic response.
  • Create a Webhook Registers a URL that Gleap calls for the chosen Events. Add a Description to label it. The response includes the Secret.
  • Create or Update a Contact Creates a contact or updates an existing one. Use User ID for your own ID of the contact and add Email, Phone, Company Name, Plan, Value, Tags or Custom Data. New Tags replace the old ones.
  • Delete a Company Deletes a company from Gleap, which cannot be undone.
  • Delete a Contact Deletes a person from your Gleap contacts.
  • Delete a Contact Memory Entry Removes a remembered fact that was saved on a contact.
  • Delete a Draft Reply Removes the unsent reply draft saved on a ticket.
  • Delete a Help Center Article Deletes one article inside a help center collection.
  • Delete a Help Center Collection Removes a help center collection from Gleap.
  • Delete a Message Deletes a message from a ticket conversation.
  • Delete a Message Template Removes a saved reply template from Gleap.
  • Delete a News Item Deletes a news item from your in-app announcements.
  • Delete a Pipeline Entry Removes one entry from a pipeline board in Gleap.
  • Delete a Survey Response Removes a single answer set from a survey.
  • Delete a Team Removes a support team from your Gleap workspace.
  • Delete a Ticket Deletes a ticket from Gleap. This cannot be undone.
  • Delete a Ticket Type Deletes a ticket type board from your project.
  • Delete a Webhook Removes a webhook subscription from your Gleap project.
  • Delete AI Content Deletes one knowledge entry the Gleap AI used to answer questions.
  • Delete an Invitation Cancels an invitation to join the project in Gleap.
  • Find Similar Tickets Looks for tickets that resemble a Query, skipping the Exclude Ticket ID if given. Use Limit to cap the matches.
  • Find Tickets by Contact Finds the tickets of one contact by Email, User ID or Phone. Use Limit to read fewer.
  • Get a Company Retrieves a company with its Name, Plan, Domain and Value.
  • Get a Contact Retrieves a contact by Contact ID with Name, Email, Phone and Company Name.
  • Get a Contact by User ID Looks up a contact from your own User ID instead of the Gleap contact ID.
  • Get a Contact Memory Entry Reads one remembered note of a contact, with its Name and Content.
  • Get a Help Center Article Reads an article from a collection with its Title, Description and Version.
  • Get a Help Center Article Draft Reads the unpublished draft of an article, with its Title, Description and Version.
  • Get a Help Center Collection Reads a collection with its Title and Description, and whether it is Unpublished.
  • Get a Message Template Reads a saved reply with its Title and Content.
  • Get a Message Thread Reads the replies underneath one message. Use Limit to read fewer.
  • Get a News Item Fetches a news item and shows its Subject and Status.
  • Get a Pipeline Shows a pipeline with its Name, Record Type and Lanes.
  • Get a Pipeline Entry Reads one board entry and the Lane ID it sits in.
  • Get a Statistics Bar Chart Produces bar chart data for a Chart Type. Narrow the range with Start Date, End Date, Time Zone and Group By, and cap the bars with Limit.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with AlfaDocs and Gleap integrations. Pick any from the list below if the current combination isn't the one you need.

Automate AlfaDocs and Gleap on WEXTL®

Claim your 3-day trial to build AlfaDocs with Gleap integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting AlfaDocs and Gleap.

How do I connect AlfaDocs and Gleap?

Connect your AlfaDocs and Gleap accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between AlfaDocs and Gleap?

Example: when the "Watch Appointments" trigger in AlfaDocs fires, WEXTL can "Add a Company Member" in Gleap. AlfaDocs has 2 triggers (including Watch Appointments and Watch Patients). Gleap has 148 actions (including Add a Company Member, Add a Contact Memory, and Add AI Content). Add filters and transforms between steps when you need them.[1]

Can AlfaDocs trigger actions in Gleap, and Gleap in AlfaDocs?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate AlfaDocs and Gleap?

No. AlfaDocs-to-Gleap automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does AlfaDocs integrate with Gleap in real time?

Yes. Trigger-based automations start the moment AlfaDocs (or Gleap) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a AlfaDocs + Gleap integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect AlfaDocs with Gleap?

You can build your AlfaDocs + Gleap automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the AlfaDocs and Gleap integration.

  1. AlfaDocs and Gleap integration source code, module specs and credentials implementation.
  2. Our AlfaDocs and Gleap integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for AlfaDocs and Gleap, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. AlfaDocs integration information
  6. Gleap integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted AlfaDocs and Gleap integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore AlfaDocs and Gleap, or get started