Elastic and Ninox Integration

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

Build database workflows between Elastic and Ninox on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

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

Learn about Elastic and Ninox

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

  • Elastic

    • Database
    • 58 searches
    • 65 actions

    Distributed search and analytics engine for documents, logs, and metrics.[5]

  • Ninox

    • Database
    • 2 triggers
    • 14 searches
    • 9 actions

    Low-code database and workflow platform.[6]

How to connect Elastic to Ninox

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

How does the integration between Elastic and Ninox work in WEXTL?

WEXTL exposes actions and triggers for Elastic and Ninox 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.

Ninox triggersElastic actions

Ninox modules

  • Create a Record Inserts a row in a Ninox table, with one input per field of the chosen Table. Use Extra Fields for references or multiple choice columns. Returns the new ID and Sequence.
  • Create or Update a Record With an ID Writes a record to a Ninox table at one numeric Record ID. A free ID creates the record and an existing ID updates it. Extra Fields cover columns the form lacks.
  • Delete a File Deletes one attachment from a record. Turn on Confirm to acknowledge that the file cannot be recovered afterwards.
  • Delete a Record Deletes a record in a table. Switch Confirm on to confirm the call, because a deleted record cannot be undone.
  • Delete Records Removes many records from a table in one request. Use Confirm to approve it, as the deletion is permanent.
  • Download a File Fetches the content of an attachment on a record. Output holds the File, its File Name and Content Type.
  • Find a Record Looks in a table for the first record whose fields equal every value of Filters. Use Choice Style to set how choice fields are returned.
  • Get a Database Retrieves one Ninox database with its Settings, Schema and Version. Add the Schema Password for a password protected schema, otherwise Ninox answers with an encrypted schema.
  • Get a Record Shows a single record of a table with its fields, Created At and Modified At. Use Choice Style to switch how choice fields are returned.
  • Get a Table Pulls the definition of one table in a database, giving its ID, Name and Fields.
  • Get a Team Finds one Ninox team and returns its ID and Name.
  • List Database Changes Lists what changed anywhere in a database after a sequence number, taken from the seq of an earlier answer or of a record. The output holds Updates, Removes and the next Sequence.
  • List Databases Shows the databases of a team, each with its ID and Name. Use Limit to set the maximum number of databases returned.
  • List Record Files Shows the files attached to one record, each with its Name, Content Type, Size and Modified Date. Use Limit to cap how many files are returned.
  • List Table Changes Lists the changes in one table made after a sequence number. Use Since Sequence to set where to start. Each result gives the Updates, the Removes and a fresh Sequence.
  • List Tables Enumerates the tables inside a database with their ID, Name and Fields. Use Limit to decide how many tables come out.
  • List Teams Retrieves Ninox teams, each with an ID and Name. Use Limit to bound the number of teams.
  • Make an API Call Sends a free-form request to the Ninox REST API, signed with your saved credential.
  • Run a Query Executes a read-only Ninox script against a database and returns its Result. Use Query to write the script, such as a select on one table.
  • Run a Script Runs a Ninox script that may create, change or delete data and returns its Result. Turn on Confirm to run it, because the changes cannot be undone. On a private cloud the key needs the admin role.
  • Search Records Returns records from a table, each as its own result. Narrow them with Filters or a Script Filter, sort with Order By, keep only those above an ID using Only After Record ID, and set Limit for the count.
  • Update a Record Changes fields on a record that already exists. Use Clear Fields to empty fields, which wins over values filled in on the form, and Extra Fields for columns that form does not offer.
  • Upload a File Adds a file to the attachments of a record. Map File from an earlier step such as a download or an email attachment, and use File Name to store it under another name.
  • Watch New Records Polls a table on your schedule and fires for each record created since the last check. Use Limit to set how many of the newest records the first check takes.
  • Watch Updated Records Checks a table on a schedule and fires for every record that was created or modified since the previous check. Use Limit to cap the newest records returned on the first check.

Elastic modules

  • Analyze Index Text Splits Text into search tokens using the analyzers and field mappings of one index. Use Field to analyze it the way that field would, or Analyzer, Tokenizer, Token Filters and Character Filters to try another chain.
  • Analyze Text Breaks Text into search tokens, either with an Analyzer or with a Tokenizer plus Token Filters and Character Filters. Add a Normalizer to turn the whole text into a single token for keyword fields.
  • Bulk Index Documents Runs many index, create, update and delete actions in one request, each action line followed by its document line. Add an Ingest Pipeline as default, or Require Alias to fail operations whose index is not an alias. Output includes Took (ms), Errors and Items.
  • Cancel a Task Cancels a running task. Turn on Wait for Completion to wait until the task has actually stopped.
  • Clean a Snapshot Repository Removes files from a snapshot repository that no remaining snapshot needs.
  • Clone an Index Copies a read-only Source Index to a New Index Name that does not exist yet. Pass Settings or Aliases as JSON objects for the new index, and Wait for Active Shards to wait for shard copies. Output includes Acknowledged and Index.
  • Close an Index Closes an index, or a comma-separated list or pattern of indices. Use Wait for Active Shards to wait for shard copies before the step finishes.
  • Count Documents Counts the documents that match a Query DSL object or a Lucene Query String, across all indices. Use Minimum Score, Routing or Stop After to narrow or shorten the count.
  • Count Index Documents Counts documents in a single index, with the same Query, Query String, Minimum Score and Routing options. Output has the Count and Shards.
  • Create a Component Template Saves a reusable component template under a Template Name. Fill in at least one of Settings, Mappings or Aliases to say what it contributes, and turn on Create Only to fail instead of replacing a template of the same name.
  • Create a Data Stream Makes a new data stream. An index template with data stream enabled must already match its name.
  • Create a Document Stores a new Document in a data stream or index under a Document ID, failing with a conflict if that ID already exists. Use Ingest Pipeline to transform it first and Routing to pick the shard.
  • Create a Snapshot Takes a snapshot in a Repository under a Snapshot Name. Narrow it with Indices, Feature States or Ignore Missing Indices, and turn on Wait for Completion to get its details.
  • Create a Snapshot Repository Registers a repository under a Repository Name, of a Type such as Amazon S3 or Shared file system, with its Settings. Turn Verify off to register it first and check later.
  • Create an ILM Policy Saves an index lifecycle policy from its Phases (hot, warm, cold, frozen or delete). An existing policy with the same Policy Name is replaced.
  • Create an Index Creates an index named Index Name, with optional Settings, Mappings and Aliases as JSON objects. Leave Settings empty for the cluster defaults.
  • Create an Index Alias Points an Alias Name at an index or data stream. Add a Filter to limit which documents the alias shows, or turn on Write Index to make this index the one that receives writes sent to the alias.
  • Create an Index Template Saves an index template for matching Index Patterns, with optional Component Templates, Priority, Settings, Mappings and Aliases. Turn on Data Stream to create data streams instead of plain indices.
  • Create an Ingest Pipeline Saves an ingest pipeline from its Processors, which run in order. Use On Failure for processors that run when one fails, and If Version to replace it only at a stored version.
  • Delete a Component Template Removes a component template. Elasticsearch refuses while an index template still uses it.
  • Delete a Data Stream Deletes a data stream. Its data is removed and this cannot be undone.
  • Delete a Data Stream Lifecycle Removes the lifecycle attached to a data stream in Elasticsearch.
  • Delete a Document Deletes a document held in an index. Use If Sequence Number and If Primary Term so the delete only runs when the document has not changed since.
  • Delete a Snapshot Deletes a snapshot stored in a Repository. Turn off Wait for Completion to return as soon as the deletion is scheduled.
  • Delete a Snapshot Repository Unregisters a snapshot repository from the cluster.
  • Delete an ILM Policy Removes a lifecycle policy. Elasticsearch refuses while an index still uses it.
  • Delete an Index Removes an index. This cannot be undone. Turn on Ignore Missing Index so the step succeeds when the index does not exist.
  • Delete an Index Alias Deletes the alias pointing at a data stream or index.
  • Delete an Index Template Deletes an index template used for new indices.
  • Delete an Ingest Pipeline Removes an ingest pipeline. An index that names it as its default pipeline then fails to index.
  • Delete Documents by Query Deletes all documents of an index that match a Query, stopping at Maximum Documents when that is used. Use Requests per Second to throttle the run, and On Version Conflict to Abort or Proceed.
  • Explain Allocation Explains why a shard is or is not allocated. With nothing filled in, it explains the first unassigned shard Elasticsearch finds. Turn on Include Disk Info or Include Yes Decisions for more detail.
  • Explain Document Tests a document against a Query DSL object or a Lucene Query String. Output includes Matched and Explanation.
  • Explain Index Lifecycle Reports the lifecycle state of an index, with its Policy, Phase and Age. Turn on Only Errors to see only stuck indices, or Only Managed to leave out those with no policy.
  • Flush All Indices Triggers a flush on all indices. Turn on Force to flush even when there are no changes to commit.
  • Flush Index Flushes one index, or a list or pattern of them. Turn off Wait If Ongoing to fail instead of waiting for a flush already running.
  • Force Merge Index Merges an index down to Maximum Segments per shard, where 1 gives the fastest searches. Run it only on indices that no longer receive writes.
  • Get a Component Template Reads a component template, or one per match when a wildcard is used. Output includes the Name, Version, Template and Created Date.
  • Get a Data Stream Reads a data stream, or one result per match for a pattern such as logs-*. Output includes Health, Generation, Index Template, ILM Policy and Backing Indices.
  • Get a Data Stream Lifecycle Reads the lifecycle of a data stream, giving a Data Stream and its Lifecycle for each match. Turn on Include Defaults to also show settings that keep their default value.
  • Get a Document Fetches a document by Document ID from an index. Output includes Found, Version, Source and Stored Fields. Add Source Fields to Include to return only fields like user.id, or Source Fields to Exclude to leave out a large body field.
  • Get a Document Source Fetches the stored Source of a document without its metadata, with optional Source Fields to Include and Source Fields to Exclude. Turn off Real Time to read only refreshed data.
  • Get a Mapping Returns the mapping for an index, with one result per index when a list or pattern is used.
  • Get a Node Describes a node. Output includes Node ID, Name, Host, IP, Version and Build Flavor. A filter such as master:true returns one result per match.
  • Get a Snapshot Reads snapshots from a Repository. Sort them with Sort By and Order, filter with States, and turn off Verbose for a shorter answer.
  • Get a Snapshot Repository Reads a snapshot repository, or one per match for a list or wildcard. Output includes Repository, Type, UUID and Settings.
  • Get a Task Checks the progress of a task, such as one started by Reindex Documents or Delete Documents by Query. Turn on Wait for Completion to wait, up to Timeout, until it finishes.
  • Get All Mappings Reads the field mappings of all indices as one result per Index. Use Include to pick which kinds of indices are read, and Limit to cut the number returned.
  • Get All Settings Reads the settings of all indices, with Settings and Defaults for each Index. Use Flat Settings for dotted keys instead of nested objects.
  • Get an ILM Policy Reads a lifecycle policy, or one per name when several are mapped. Output includes Policy Name, Version, Policy and In Use By.

Explore alternative integrations

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

Automate Elastic and Ninox on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Elastic and Ninox.

How do I connect Elastic and Ninox?

Connect your Elastic and Ninox 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 Elastic and Ninox?

Example: when the "Watch New Records" trigger in Ninox fires, WEXTL can "Analyze Index Text" in Elastic. Elastic has 123 actions (including Analyze Index Text, Analyze Text, and Bulk Index Documents). Ninox has 23 actions (including Create a Record, Create or Update a Record With an ID, and Delete a File). Add filters and transforms between steps when you need them.[1]

Can Elastic trigger actions in Ninox, and Ninox in Elastic?

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 Elastic and Ninox?

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

Does Elastic integrate with Ninox in real time?

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

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

References

List of sources used to gather information about the Elastic and Ninox integration.

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

How we write our apps documentation

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

Explore Elastic and Ninox, or get started