Markup AI and Vapi Integration

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

Keep Markup AI and Vapi matched by integrating their events and actions. When ai events happen in Markup AI, update the Vapi 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 Markup AI and Vapi

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

  • Markup AI

    • AI
    • 1 trigger
    • 42 searches
    • 42 actions

    Content checks that keep writing on brand, on style and on terminology.[5]

  • Vapi

    • AI
    • 57 searches
    • 76 actions

    Build and run Vapi voice assistants, manage calls and campaigns, and operate evaluation and knowledge-base resources.[6]

How to connect Markup AI to Vapi

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

How does the integration between Markup AI and Vapi work in WEXTL?

WEXTL exposes actions and triggers for Markup AI and Vapi 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.

Markup AI triggersVapi actions

Markup AI modules

  • Watch New Agent Runs Checks for agent runs at a set interval and runs once per new run. Use Limit to set how many of the newest runs from the last day the first check takes.
  • Add a Term Comment Comments on a terminology term. The result is the new history event with its type, text, user and date.
  • Add Files to a Style Check Batch Uploads up to 20 documents into a style check batch that already exists. Use Items to attach metadata for each file and Defaults to set per-batch style guide settings.
  • Add Items to a Style Check Batch Appends up to 20 text documents per call to a batch that already exists. Pass Defaults to apply settings such as the style guide to the batch.
  • Cancel an Agent Run Stops a running agent workflow and reports the Cancelled At time.
  • Contribute a Terminology Term Proposes a new term for the terminology in a given language and under chosen categories. Add a Comment or Custom Field Values to explain the suggestion.
  • Create a Brand Domain Adds a brand domain that groups term sets, with an optional Description. The result includes its Term Set Count.
  • Create a Brand Term Adds a Term of a chosen Type to a brand term set. Turn on Case Sensitive to match capitalization exactly.
  • Create a Brand Term Set Creates a term set from a Context that decides when its terms are flagged and what the replacement should be. Add starter Terms, a Term Type and a Context Polarity here.
  • Create a Style Check Batch Starts a batch of up to 20 documents for style checking. Set Webhook URL to get notified when the batch ends.
  • Create a Style Check Batch from Files Starts a style check batch from up to 20 uploaded Files. Use Items to add metadata for each file in order, and Webhook URL to get a notice when the batch ends.
  • Create a Terminology Category Adds a category of a given Category Type under a unique Name. Use Parent Category ID to nest it and Priority to set its sort position among siblings.
  • Create a Terminology Category Type Defines a type of category with a unique Name and a Display Name. Turn on Hierarchical to allow nesting, or Closed to block new top-level categories.
  • Create a Terminology Custom Field Defines a custom field for terminology records, with a Name, a Display Name and a Type. Turn on Multiline or Nullable to adjust the kind of value it takes.
  • Create a Terminology Term Adds a term to the terminology with its surface text in one language and a status. Give a Masterterm ID to attach it as a variant of an existing head term.
  • Create or Replace Terminology Entries Loads up to 500 entries from an ACTIF 1.0 document, creating new ones and replacing any that already exist.
  • Delete a Brand Domain Deletes a brand domain and confirms with its ID and a Deleted flag.
  • Delete a Brand Term Removes one brand term out of the term set it belongs to. A Deleted flag in the result confirms it.
  • Delete a Brand Term Set Deletes a whole brand term set and returns the ID of the set that was removed.
  • Delete a Terminology Category Deletes a category from the glossary and reports a Deleted flag.
  • Delete a Terminology Category Type Removes a category type. Built-in system types cannot be deleted.
  • Delete a Terminology Custom Field Removes a custom field definition. The result is the field ID plus a Deleted flag.
  • Delete a Terminology Term Deletes a single term and returns a Deleted flag with its ID.
  • Delete Terminology Entries Removes several terminology entries together, matched on their Entry IDs.
  • Download a Term Image Downloads an image stored with a term as a file, along with its File Name, Size (Bytes) and Content Type.
  • Export Brand Terms as ACTIF Downloads every brand term as an ACTIF file and returns its File Name.
  • Export Brand Terms as CSV Saves every brand term as a CSV file that opens in a spreadsheet. The Content Type of the file is returned as well.
  • Export the Terminology as ACTIF Produces the complete terminology as an ACTIF file and tells you the File Name it was given.
  • Export the Terminology as an XML Dump Generates an XML dump of the terminology that Import the Terminology XML Dump can load again. The Size (Bytes) of the dump is returned too.
  • Get a Brand Domain Reads one brand domain with its Name, Description and Term Set Count, plus who created and last updated it.
  • Get a Brand Term Fetches one term from a brand term set, showing its Type and whether it is Case Sensitive.
  • Get a Brand Term Set Looks up a term set with its Context, Term Type and Context Polarity. The Terms and Domains it holds come with it.
  • Get a Brand Voice Profile Pulls the definition of one brand voice profile, with its Identity, Bright Lines, Fingerprints and Exemplars.
  • Get a Persona Returns one reader persona with its Title, Seniority, Industry and Technical Level.
  • Get a Style Check Batch Shows a batch with its Status, Sealed state and Counts. Use Item Limit and Item Offset to page through the Items of a big batch.
  • Get a Style Check Result Gets the Result of a style check run with its Status and Check Type, to act on the findings.
  • Get a Style Guide Returns a style guide with its Language, Language Variant and Goals, and whether it is Enabled.
  • Get a Term History Lists the events recorded for a term, such as comments. Use Event Type to keep only some kinds of event.
  • Get a Terminology Concept Finds the concept a term belongs to and lists all Terms that share it.
  • Get a Terminology Job Tracks a terminology job from its Job ID, showing its Status, Stage, Term Count and any Error.
  • Get a Terminology Term Reads a single term with its Surface, Language, Status and Categories.
  • Get an Agent Fetches an agent along with its Description, Input Schema, Output Schema and Cadence. Check the Input Schema before calling Run an Agent.
  • Get an Agent Run Pulls one agent run showing its Status, Result and Check Type, and when it started and finished.
  • Get Terminology Entries Fetches up to 100 entries by Entry IDs and returns them as ACTIF XML.
  • Get the Current Terminology Job Checks whether a terminology job is running right now. The result has an Active flag and the Job itself.
  • Get the Style Agent Settings Reads the Style Agent configuration of your organization, including Style Agent Numeric Scoring and Allow User Tracking.
  • Get the Terminology Publish State Shows whether the terminology has drifted from what was last published, with the Last Published At, Last Changed At and Active Job.
  • Get the Terminology Schema Retrieves the schema that describes how the terminology is structured, delivered as ACTIF XML.
  • Get the Variant Rules Returns the Rules that control how term variants are generated.
  • Import Brand Terms Loads brand terms from a CSV or ACTIF XML File. Turn on Delete Existing Terms to wipe the current brand terms first, and the result counts the Term Sets Created.

Vapi modules

  • Attach and Ingest a File Attaches a file to a v2 knowledge base and ingests it from a Request body. Retry Indexing a Failed File is the follow-up if ingestion fails.
  • Cancel a Simulation Run Cancels a whole simulation run. Send a Request body along with the Simulation run ID.
  • Cancel a Simulation Run Item Cancels one item of a simulation run. Use Simulation run ID and Item ID to say which, and send a Request body with the call.
  • Create a Board Builds a reporting board out of a Request body. Get Boards lists it with the others.
  • Create a Call Creates a call defined by a Request body, with its new Status in the result.
  • Create a Campaign V2 Defines a campaign on the v2 endpoint using a Request body, returning its ID and Name.
  • Create a Chat Opens a chat as described by a Request body, returning its ID, Status and Data.
  • Create a Chat (OpenAI Compatible) Sends a Request body to the OpenAI-compatible chat responses endpoint and returns the Data.
  • Create a Knowledge Base V2 Makes a v2 knowledge base using a Request body. Attach and Ingest a File adds files to it afterwards.
  • Create a Personality Adds a simulation personality using a Request body, then reports its Name.
  • Create a Phone Number Registers a phone number in Vapi with a Request body, reporting its ID and Status.
  • Create a Provider Resource Creates one resource for a Provider and Resource name from a Request body, and returns its Data.
  • Create a Scenario Builds a simulation scenario by hand from a Request body. Generate Scenarios with AI creates them with AI instead.
  • Create a Scorecard Defines an observability scorecard through a Request body.
  • Create a Session Opens a session built from a Request body, reporting its Status.
  • Create a Simulation Sets up a simulation as laid out in a Request body, giving its Name.
  • Create a Simulation Run Starts a run of simulations with a Request body, reporting the run ID.
  • Create a Simulation Suite Creates a suite of simulations from a Request body and reports the new ID.
  • Create a Squad Adds a squad via a Request body. List Squads shows it with the others.
  • Create a Structured Output Stores a structured output via a Request body, then reports its Name.
  • Create a Tool Registers a tool described in a Request body, reporting its Status.
  • Create an Assistant Adds an assistant to Vapi from a Request body, with its ID and Name in the result.
  • Create an Eval Registers an eval from the details in a Request body, then reports its Updated at time.
  • Create an Eval Run Submits an eval run based on a Request body, with its Status in the result.
  • Create an Insight Saves a reporting insight built from a Request body, with its Name in the result.
  • Create Analytics Queries Submits analytics queries to Vapi in a Request body and returns the Data of the result.
  • Delete a Board Removes a reporting board that is saved in Vapi.
  • Delete a Call Removes one call from your Vapi data and returns its Status.
  • Delete a Campaign V2 Removes a campaign on the v2 endpoint and returns its ID.
  • Delete a Chat Removes a chat, leaving only its ID in the result.
  • Delete a File Deletes a file kept in Vapi and returns its ID.
  • Delete a Knowledge Base V2 Deletes a knowledge base through the v2 API, returning its Status.
  • Delete a Personality Removes a simulation personality and returns its Name.
  • Delete a Phone Number Deletes a phone number from Vapi and returns its Status.
  • Delete a Provider Resource Deletes a resource that sits under a Provider and Resource name.
  • Delete a Scenario Deletes a simulation scenario in Vapi.
  • Delete a Scorecard Removes an observability scorecard, with its Name in the result.
  • Delete a Session Deletes a session from Vapi and reports its Status.
  • Delete a Simulation Deletes one simulation and returns its Status.
  • Delete a Simulation Suite Deletes a simulation suite in Vapi and reports its ID.
  • Delete a Squad Deletes a squad from Vapi, with its Name in the result.
  • Delete a Structured Output Removes a structured output and returns its Data.
  • Delete a Tool Deletes one tool and returns its Name.
  • Delete an Assistant Removes an assistant from Vapi and reports its ID and Name.
  • Delete an Eval Removes an eval that lives in Vapi.
  • Delete an Eval Run Removes one eval run and reports its Name.
  • Delete an Insight Removes an insight saved in reporting.
  • Detach a File Detaches a file from a v2 knowledge base.
  • Download a Call Assistant Recording Downloads the assistant recording of a call, returning Data (base64) and the Content type.
  • Download a Call Customer Recording Fetches the customer recording for a call as Data (base64) along with its Content type.

Explore alternative integrations

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

Automate Markup AI and Vapi on WEXTL®

Claim your 3-day trial to build Markup AI with Vapi integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Markup AI and Vapi.

How do I connect Markup AI and Vapi?

Connect your Markup AI and Vapi 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 Markup AI and Vapi?

Example: when the "Watch New Agent Runs" trigger in Markup AI fires, WEXTL can "Attach and Ingest a File" in Vapi. Markup AI has 1 trigger (including Watch New Agent Runs). Vapi has 133 actions (including Attach and Ingest a File, Cancel a Simulation Run, and Cancel a Simulation Run Item). Add filters and transforms between steps when you need them.[1]

Can Markup AI trigger actions in Vapi, and Vapi in Markup AI?

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 Markup AI and Vapi?

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

Does Markup AI integrate with Vapi in real time?

Yes. Trigger-based automations start the moment Markup AI (or Vapi) 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 Markup AI + Vapi 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 Markup AI with Vapi?

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

References

List of sources used to gather information about the Markup AI and Vapi integration.

  1. Markup AI and Vapi integration source code, module specs and credentials implementation.
  2. Our Markup AI and Vapi integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Markup AI and Vapi, 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. Markup AI integration information
  6. Vapi integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

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

Explore Markup AI and Vapi, or get started