Daktela Make integrationAutomate Daktela with Make.

This module adds a new record to a Daktela campaign, which puts a lead in front of your agents without anyone typing it in by hand. The record then follows the campaign's usual flow.

Posting a comment on an existing ticket gives the agent context from another system right where they work, instead of in a separate tab or an email thread.

With Create a Contact, a person known elsewhere shows up in Daktela as a CRM contact, so agents recognize the caller instead of starting from a blank screen.

Create a CRM Record logs a new entry in the Daktela CRM from data captured in another tool, which saves agents from retyping deals or cases they did not start themselves.

An account in Daktela groups the people and cases of one customer company. This module creates it for you, so the structure exists before the first ticket or contact needs a home.

Create a Ticket opens a case in Daktela from anything that happens outside it: a form message, a failed payment, an alert from a monitoring tool. The agent then treats it like any other ticket.

Get a Campaign Record fetches one campaign record in full, so later modules can use its details: the lead, the outcome, whatever your campaign stores.

Reading a single contact from Daktela is what this module does, which gives later steps the name, company or other details stored on that person.

Get a CRM Record pulls one Daktela CRM record into the scenario, useful when the data you received is a pointer rather than the record itself.

This one retrieves a specific Daktela account, the customer company, with the information you keep on it, so a later module can use the company name or its details.

Get a Ticket reads the latest version of one Daktela ticket, handy when the scenario has been running for a while and the case may have moved since the trigger saw it.

Make a Call starts a call through Daktela from your scenario, turning an event in another tool into a phone conversation instead of a task someone has to remember.

Make an API Call is the escape hatch: it lets you call any endpoint of the Daktela API with the connection you already have, for everything the other 21 modules do not cover.

Sending an email through Daktela keeps the message inside the contact center, where agents already see customer exchanges, rather than in a separate mailbox.

Send an SMS pushes a short text message out through Daktela, a simple way to reach an agent on call or a customer who does not read email.

Set a Pause changes a pause setting in Daktela from inside your scenario. Make describes it in two words, so open the module after connecting to see exactly what it lets you set.

Update a Campaign Record changes an existing record in a Daktela campaign, so information collected elsewhere lands on the lead agents are about to call.

Keeping contact details current is the whole job here: the module rewrites an existing Daktela contact with the data another tool holds, so agents never call an old number.

Update a CRM Record writes new values on an existing Daktela CRM record, bringing a deal or a case up to date without an agent retyping it.

Update an Account refreshes a customer company in Daktela, the address, the plan or any detail you track, from the tool where that information changes first.

Update a Ticket moves a Daktela case forward from the outside: you can change it when something is resolved in another tool, without an agent reopening it by hand.