Elastic and Zite Integration

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

Connect Elastic and Zite to automate database workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

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

Learn about Elastic and Zite

Detailed info you need to know about Elastic and Zite 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]

  • Zite

    • Database
    • 1 trigger
    • 18 searches
    • 29 actions

    App platform with a shared database, backend workflows and a build API.[6]

How to connect Elastic to Zite

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

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

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

Zite triggersElastic actions

Zite modules

  • Check a Build Session Runs checks on the apps of a build session. Use App ID to check only one. Reports Diagnostics, Endpoint Errors and any Unchecked Apps.
  • Commit Session Changes Saves the work of a build session as a commit with your Commit Message. Reports the Commit Sha and the Changed Apps.
  • Create a Database Sets up a Zite database called Name. Add Tables to create tables together with their fields, each given a Table Name and field Type.
  • Create a Field Adds a column to a table of a Database, defined by its Name and Type. Use Template (JSON) for settings that belong to one field type.
  • Create a Record Inserts one row into a Database table. Fill Fields one by one or pass a whole Record (JSON) object, and turn on Strict to reject values that would be coerced.
  • Create a Table Builds a table for a Database from a Name and its Fields, where the first field becomes the primary one.
  • Create a Workspace Opens a workspace, which also creates a database with the same Name. Build tools need a paid Zite plan after the 7-day trial.
  • Create a Zite from a Prompt Has the Zite agent build an app from a written Prompt of up to 10,000 characters. Attach up to 20 Files and set a Theme or Name to steer it. The Zite ID and a Claim URL are returned.
  • Create an App Adds a new app to a build session under a Name. Set Access Mode to make it available to your organization or deploy it to a public subdomain.
  • Create Records in Bulk Writes up to 100 Records into a Database table at once. Fill Match On to update rows that already match instead of adding duplicates.
  • Delete a Database Removes a whole Zite database from the account.
  • Delete a Field Deletes a column from a table.
  • Delete a Record Removes a single row from a table by its Record ID.
  • Delete a Table Deletes a table of your choice from the Database.
  • Delete Records in Bulk Removes up to 100 rows of a table in one request, listed by their Record IDs, and returns the Deleted Count.
  • Edit a File Swaps Old Text for New Text inside a file of the session. The old snippet must match exactly once, and the call reports whether it was Replaced.
  • Get a Database Pulls a single database with its Tables and Workspace ID.
  • Get a Record Reads one row by Record ID. Use Fields to return only some columns.
  • Get a Run Fetches a single execution of an app from a Workspace by Run ID, with its Mode and Duration Ms.
  • Get a Workspace Returns a workspace along with its Apps. Add a Session ID to read the project overview as well.
  • Get an App Looks up one app inside a Workspace. You get its Build Status, any Build Error and its Access Mode.
  • Get Records Aggregate Computes an Operation over one Field, such as a sum or average on a number column. Use Group By for one result per value, and Filter (JSON) to count only some rows.
  • Get SQL Schema Describes the Tables of a database and its Link Tables, ready for writing queries. Turn off Include Fields for a short outline.
  • List Databases Shows the databases of your Zite account, each with its URL and Workspace ID.
  • List Fields Returns the columns of one table, with their Type and Order.
  • List Files Lists the file paths inside a build session, giving one Path per item.
  • List Records Pulls rows from a Database table. Use Filter (JSON) and Sort to shape the result, Fields to keep some columns, and Limit to stop after a set number.
  • List Runs Browses executions of an app in a Workspace. Narrow them by Status or Environment, and set Hours Back to look up to one week into the past.
  • List Webhooks Shows the webhooks registered on a Database, each with its Events and the Table Ids it covers.
  • List Workspace Apps Enumerates the apps that live in a Workspace and flags which ones are Published.
  • List Workspaces Fetches every workspace available to you, including its Apps and Overview.
  • Make an API Call Makes an authorized free-form request to the Zite REST API with your saved credential.
  • Open a Build Session Starts a build session in a Workspace so later steps can read, edit and commit its files. The Session ID those steps need is returned.
  • Publish a Deployment Publishes an app from a Workspace. Returns the Snapshot ID, the Commit Sha and the Access Mode of what went out.
  • Read a File Opens one file of a build session and returns its Content.
  • Run a Command Executes a shell Command in the checkout of a session and reports its Stdout, Stderr and Exit Code.
  • Run SQL Query Runs a read-only SELECT statement against a database. Use Bind Values for $1 and $2 placeholders and Statement Timeout (ms) to bound the run time. Flags a Truncated result.
  • Search Files Finds a regular expression Pattern across session files. Restrict it to a Path or a Glob, and ask for Context Lines around each match.
  • Update a Field Renames a column with Name, changes its Type, or edits its Template (options are merged).
  • Update a Record Changes one row by Record ID. Fields you leave out stay as they are, and you can empty chosen ones with Clear Fields.
  • Update a Table Renames a table, repositions it with Order, or picks a new Primary Field.
  • Update Records in Bulk Edits up to 100 Records at once, each needing its Record ID and the fields to change.
  • Upload a CSV File Saves a CSV File in Zite and returns its URL and Storage Key.
  • Upload a Large Attachment Handles a File too big for the regular upload and saves it into an attachment field, returning its URL and Size.
  • Upload an Attachment Stores a File under its File Name in an attachment column and returns the URL, Size and MIME Type. Bigger files go through Upload a Large Attachment.
  • Upload an Excel File Sends a spreadsheet File to Zite storage and returns a link to it.
  • Watch Events Fires instantly through a webhook whenever Zite sends an event, passing on the Event, its Timestamp and its Data.
  • Write a File Creates or overwrites a file at Path with the full Content. Reports the Bytes written.

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 Zite integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Elastic and Zite on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Elastic and Zite.

How do I connect Elastic and Zite?

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

Example: when the "Watch Events" trigger in Zite fires, WEXTL can "Analyze Index Text" in Elastic. Elastic has 123 actions (including Analyze Index Text, Analyze Text, and Bulk Index Documents). Zite has 47 actions (including Check a Build Session, Commit Session Changes, and Create a Database). Add filters and transforms between steps when you need them.[1]

Can Elastic trigger actions in Zite, and Zite 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 Zite?

No. Elastic-to-Zite 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 Zite in real time?

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

You can build your Elastic + Zite 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 Zite integration.

  1. Elastic and Zite integration source code, module specs and credentials implementation.
  2. Our Elastic and Zite integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Elastic and Zite, 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. Zite 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 Zite integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Elastic and Zite, or get started