Kadoa and Splunk Integration

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

Keep Kadoa and Splunk matched by integrating their events and actions. When developer tools events happen in Kadoa, update the Splunk 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 Kadoa and Splunk

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

  • Kadoa

    • Developer Tools
    • 2 triggers
    • 59 searches
    • 57 actions

    Web data extraction workflows with runs, data changes, schemas, templates and notifications.[5]

  • Splunk

    • Developer Tools
    • 2 triggers
    • 72 searches
    • 76 actions

    Run Splunk searches, manage saved searches and users, and send events via HEC.[6]

How to connect Kadoa to Splunk

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

How does the integration between Kadoa and Splunk work in WEXTL?

WEXTL exposes actions and triggers for Kadoa and Splunk 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.

Kadoa triggersSplunk actions

Kadoa modules

  • Add Workflows to a Template Links existing workflows to a template and reports the Linked Count and the Workflow Ids. Turn on Force to relink workflows that are already linked to another template.
  • Answer an Agent Question Replies to a question that the Kadoa agent raised during a session, using Answers (JSON) for the Question ID. Add a Thread ID to keep the reply in one thread.
  • Approve a Workflow for Compliance Marks a workflow as approved in the compliance review. Returns the New State of the workflow.
  • Archive a Template Archives a template and detaches the workflows linked to it. Returns the Unlinked Workflow Count.
  • Create a Notification Channel Adds a place for Kadoa notifications to go, from a Name, a Channel Type and a Config (JSON) for that type.
  • Create a Schema Defines the data fields a workflow extracts, from a Name and Fields, for an optional Entity. Returns the Schema Id and Created At.
  • Create a Scrape Fetches a page from the URL with browser options such as Method, Wait Until, Device, Proxy or Format. Set Timeout to limit how long the fetch may take.
  • Create a Secret Connection Registers a link to a secrets provider under a Display Name, using an Auth Mode. Fill Project ID and Service Account JSON for providers that ask for them.
  • Create a Support Issue Opens a ticket with the Kadoa support team from a Title, Category and Description. Add a Priority, Files (JSON) or a related Workflow ID for context.
  • Create a Template Saves an empty template under a Name, with an optional Description, ready to receive versions and linked workflows.
  • Create a Template Copy Duplicates a template into a new one. Give the copy its own Name or let it default.
  • Create a Template from a Workflow Promotes a workflow into a reusable template. Use Include Parts to choose what is copied, and Name or Description to label it.
  • Create a Template Version Publishes a new revision of a template with a changed Prompt, Schema ID, Frequency (JSON), Notifications (JSON) or Record Limit.
  • Create a Test Notification Sends a sample notification for the chosen Event Type to check delivery. Add a Workflow ID to test for one workflow.
  • Create a Variable Stores a named Key with a Value and Data Type for workflows to read. Set Management Mode and Provider Connection ID to fetch the value from a secrets provider.
  • Create a Workflow Builds an extraction workflow for the Website URLs. Give it a Name, Prompt or Schema for what to extract, and set Run Interval or Cron Schedules to repeat it. Link a Template to reuse its setup.
  • Create a Workflow Data Export Prepares an export of the extracted data of a workflow, in a Format. Narrow it with Run ID, Filters or Row Ids, and arrange rows with Sort By and Order.
  • Create a Workflow Data Query Writes an SQL query for the data in a workflow from a Prompt, with Columns (JSON) and Sample Rows (JSON) as context. Returns the Sql and an Explanation.
  • Create a Workflow Trigger Starts a Target Workflow ID whenever the chosen Event Type happens in another workflow. Turn on Enabled to activate it.
  • Create an Agent Session Starts a conversation with the Kadoa agent from a Prompt, which can build or change a workflow. Set Template ID, Product Type, Tags or Notification Channel Ids to guide what it creates.
  • Create an Agent Session for a Workflow Opens an agent session tied to one workflow, so later prompts work on that workflow.
  • Create an Agent Update Request for a Workflow Asks the agent to change an existing workflow as described by Prompt. Use Thread ID to continue an earlier discussion.
  • Create Notification Settings Subscribes to an Event Type with an Event Configuration (JSON). Restrict it to a Workflow ID, send to chosen Channel Ids and set Enabled to activate it.
  • Delete a Notification Channel Deletes a channel that Kadoa alerts are sent to.
  • Delete a Schema Deletes a stored data schema and reports Success.
  • Delete a Secret Connection Removes the saved link to a secrets provider.
  • Delete a Variable Deletes a stored variable that workflows read.
  • Delete a Workflow Removes an extraction workflow from your Kadoa workspace.
  • Delete a Workflow Trigger Deletes a chained trigger of a workflow, using its Trigger ID.
  • Delete an Agent Session Deletes a session of the Kadoa agent by its Session ID.
  • Delete Data Quality Rules for a Field Removes the quality rules that apply to a single Field Name in a workflow and shows the resulting Rules.
  • Delete Notification Settings Removes one alert rule from your Kadoa account.
  • Download a Change PDF Fetches the PDF file attached to a data change, addressed by its Encoded Path.
  • Download a Data Change CSV Gets the CSV of one data change for a workflow, by Change ID. Add Expires and Sig to pass the signed link values.
  • Download a File Downloads a stored Kadoa file and makes its content available to later steps, using its File Name.
  • Download a Workflow Data Export Fetches the file of an export that was prepared earlier, using the Export ID from Create a Workflow Data Export.
  • Download a Workflow Metadata CSV Exports metadata of your workflows as a CSV file. Use Time Filter to restrict the period covered.
  • Download a Workflow Run CSV Gets the CSV produced by a single run of a workflow, for a Job ID. Add Expires and Sig to pass the signed link values.
  • Download Activity Events CSV Exports the account activity log. Limit it to a Workflow ID, User ID, Start Date, End Date, Relative Time, Event Types, Interfaces or Resource Types.
  • Download Files as ZIP Packs several stored Files into a single ZIP archive and downloads it.
  • Download the Workflow Data as Parquet Downloads the extracted data of a workflow in Parquet format. Use Run ID to take one specific run.
  • Get a Data Change Returns one detected change in extracted data by Change ID, with its Differences and whether the Data Pending approval.
  • Get a Notification Channel Looks up a single alert destination. Turn on Include Configurations to see how it is set up.
  • Get a Notification Event Type Describes one kind of event that can trigger an alert, by its Event Type.
  • Get a Schema Returns a saved data schema with the fields it defines.
  • Get a Template Fetches one workflow template by its Template ID and returns its Data.
  • Get a Template Schema Change Preview Shows how a linked workflow would change if moved to a Target Version of a template, before you apply it.
  • Get a Variable Retrieves one stored variable, a named value that workflows read, by Variable ID.
  • Get a Workflow Loads an extraction workflow, returning its Name, Description, State and Display State.
  • Get a Workflow Job Checks one run of a workflow for a Job ID, returning its State, Started At and Finished At.

Splunk modules

  • Acknowledge a Saved Search Calls the acknowledge action of one saved search, using the Name from List Saved Searches. Use Additional Fields to add JSON properties to that call.
  • Control a Search Job Posts the Search text to the control endpoint of the search job with the Sid from List Search Jobs.
  • Create a Calculated Field Defines a calculated field in the props settings, optionally under a Name of your choice. Use Additional Fields to include the JSON definition of the field.
  • Create a Data Model Saves a data model in Splunk, with an optional Name. Use Additional Fields to send its JSON definition.
  • Create a Field Alias Registers an alias for a field. Use Additional Fields to specify the mapping as JSON.
  • Create a Field Extraction Adds a rule that pulls fields out of events, stored in the props settings. Extra JSON options can be added with Additional Fields.
  • Create a KV Store Collection Adds a collection to the KV store configuration. Use Additional Fields to define its fields as JSON.
  • Create a KV Store Record Writes a new record into a KV store collection from the Collection field. Use Additional Fields to provide the record values as JSON.
  • Create a Local App Creates an app on the local Splunk server. Use Additional Fields to add app settings as JSON.
  • Create a Lookup Creates an entry for a lookup table file. Use Additional Fields to list the file details as JSON.
  • Create a Macro Saves a search macro. Use Additional Fields to configure the macro definition as JSON.
  • Create a Message Posts a message to the Splunk messages list from a sender to a recipient. Add Text for its content, together with To and From.
  • Create a Panel Adds a panel to the Splunk UI configuration. Use Additional Fields to define the panel contents as JSON.
  • Create a Role Defines an authorization role. Use Additional Fields to attach capabilities as JSON.
  • Create a Saved Search Keeps a search for repeat use. Use Additional Fields to include the search string and any schedule as JSON.
  • Create a Search Job Starts a search job that runs the Search query. Use Maximum Number of Results to cap the rows, which can run up to one page over.
  • Create a Tag Creates a tag for use in searches. Use Additional Fields to pass tag data as JSON and Maximum Number of Results to cap the rows returned.
  • Create a TCP Input Creates a raw TCP port input for receiving network data. Use Additional Fields to set port options as JSON.
  • Create a Token Creates an authorization token. Use Additional Fields to name the token details as JSON.
  • Create a Transform Adds an extraction transform that field extractions can refer to. Use Additional Fields to put its extraction settings into the JSON.
  • Create a UDP Input Creates a UDP input that listens for incoming datagrams. Use Additional Fields to describe port settings as JSON.
  • Create a User Adds a user account to Splunk authentication. Use Additional Fields to provide the details of the user as JSON.
  • Create a View Adds a UI view. Use Additional Fields to hand over the view definition as JSON.
  • Create a Workflow Action Creates a workflow action that appears in the Splunk interface. Use Additional Fields to attach its settings as JSON.
  • Create an Automatic Lookup Adds an automatic lookup definition to the Splunk props configuration. Use Additional Fields to supply lookup options as JSON.
  • Create an Event Type Creates an event type. Use Body to send the event type definition as JSON.
  • Create an HTTP Input Opens an HTTP input on the server to receive data. Use Additional Fields to give its options as JSON.
  • Create an Index Creates an index to hold ingested data. Add a Name, and use Additional Fields for other index settings in JSON.
  • Delete a Fired Alert Deletes a record of a triggered alert from Splunk.
  • Delete a KV Store Collection Removes a collection definition from the KV store.
  • Delete a KV Store Record Deletes the record that matches Key within the Collection of your KV store.
  • Delete a Local App Removes an app that is installed on the local Splunk server.
  • Delete a Lookup Removes the lookup table file entry for a lookup.
  • Delete a Macro Removes a search macro from the Splunk configuration.
  • Delete a Message Deletes a message that Splunk shows in its messages list.
  • Delete a Role Removes an authorization role from Splunk.
  • Delete a Saved Search Deletes a stored search from the Splunk server.
  • Delete a Search Job Removes a search job from the Splunk instance.
  • Delete a Tag Deletes a search tag from Splunk and gets its Status.
  • Delete a User Removes the account of a Splunk user.
  • Delete an Event Type Deletes an event type definition from the Splunk server.
  • Delete an HTTP Input Deletes an HTTP data input configured on the Splunk server.
  • Delete an Index Removes an index from the Splunk server.
  • Disable a Saved Search Turns off one saved search through its disable action, for the Name that List Saved Searches shows.
  • Dispatch a Saved Search Runs a saved search right away through its dispatch action. Use Additional Fields to include dispatch options as JSON.
  • Enable a Local App Posts Additional Fields as JSON to one local app, at the same address that Update a Local App uses. Send the app settings you want applied.
  • Enable a Saved Search Turns a saved search back on through its enable action, for the Name that List Saved Searches shows.
  • Get a Config Reads the stored settings of a configuration file from the properties service. List Configs shows which files exist.
  • Get a Data Model Retrieves the definition of a single data model from Splunk, such as one browsed through List Data Models.
  • Get a Field Alias Fetches one field alias entry from the props settings.

Explore alternative integrations

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

Automate Kadoa and Splunk on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Kadoa and Splunk.

How do I connect Kadoa and Splunk?

Connect your Kadoa and Splunk 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 Kadoa and Splunk?

Example: when the "Watch Events (Instant)" trigger in Kadoa fires, WEXTL can "Acknowledge a Saved Search" in Splunk. Kadoa has 2 triggers (including Watch Events (Instant) and Watch New Data Changes). Splunk has 148 actions (including Acknowledge a Saved Search, Control a Search Job, and Create a Calculated Field). Add filters and transforms between steps when you need them.[1]

Can Kadoa trigger actions in Splunk, and Splunk in Kadoa?

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 Kadoa and Splunk?

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

Does Kadoa integrate with Splunk in real time?

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

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

References

List of sources used to gather information about the Kadoa and Splunk integration.

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

How we write our apps documentation

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

Explore Kadoa and Splunk, or get started