Connect Parallel integrations

Verified

Web search, page extraction and deep research for agents and workflows, connected to WEXTL workflows and AI agents. Chain Parallel steps with the rest of your stack in one visual workflow. Combine Get a FindAll Run with Get a FindAll Run Result or Get a FindAll Run Schema so repetitive work keeps moving on its own.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region
  • Parallel
  • WEXTL
  • DocsBot
  • Glam AI
  • Groq AI
  • Krisp Portal
  • Runway ML
  • OpenMic AI
  • LingvaNex
  • Rytr
  • Perplexity
  • Fathom AI
  • Langfuse
  • Slazzer
  • Parseur
  • Exa AI
  • Minimax
  • Bigjpg
  • Mureka AI
  • Dappier
  • Microsoft Copilot

Supported triggers and actions for Parallel integration

Triggers can detect changes in Parallel and run actions that can create, search or modify data inside Parallel automatically[3], exactly how you set them.

  • Watch Events Starts the workflow when Parallel posts a webhook event, with its Event Type, Timestamp and Data.
  • Get a FindAll Run Checks how a FindAll run is going and shows its Status, Generator and Metadata.
  • Get a FindAll Run Result Downloads the Candidates found by a FindAll run along with the Run record itself.
  • Get a FindAll Run Schema Shows how a FindAll run was set up, from its Objective and Entity Type to Match Conditions and Enrichments.
  • Get a Monitor Looks up one monitor to see its Frequency, Processor, Webhook, Settings and when it last ran.
  • Get a Task Group Reads the Status and Metadata of a batch of task runs, for the Task Group ID that Create a Task Group gave you.
  • Get a Task Group Run Fetches one run that belongs to a group, using both the Task Group ID and the Run ID. Its Status tells you how far along it is.
  • Get a Task Run Polls a task run by Run ID to see its Status, its Processor and whether it is still active.
  • Get a Task Run Input Recalls what a task run was asked, returning its Input, Task Spec and Processor.
  • Get a Task Run Result Collects the Output of a task run. Use Wait Seconds, up to 600, to hold the call until the run finishes.
  • Get Monitor Stats Counts all monitors in the account as a Total, with a split by processor.
  • List Monitor Events Lists what a monitor has detected, each with Event Type, Event Date and Output. Use Event Group ID to stay with one execution and Include Completions to see runs without changes.
  • List Monitors Lists monitors with their Type, Status and Frequency, up to Limit. Without a Status filter only active monitors appear.
  • Retrieve Memories Searches stored memories. Use Query to narrow what is found, Kind and Since to filter by type and date, and Limit to hold the count between 1 and 25.
  • Search Entities Quickly locates entities of a given Entity Type that fit an Objective. Use Match Limit to set how many are returned, from 5 to 1000.
  • Search Images Finds pictures for one or more Search Queries. Use Objective to sharpen the ranking, Mode to trade speed against depth and Max Results to limit the haul.
  • Search Places Looks for businesses and venues matching a Query around a Location or a Latitude and Longitude. Turn on Open Now or set Max Distance (km) to narrow the hits.
  • Search Web Runs web searches for short Search Queries and returns Results with excerpts. Restrict sources with Include Domains, and bound excerpt size with Max Characters.
  • Add an Enrichment to a FindAll Run Extends the candidates of a FindAll run with extra data described by an Output Schema. Use Processor to choose the tier and MCP Servers to let the enrichment call outside servers.
  • Add Runs to a Task Group Queues several task runs in one batch from a JSON array of Inputs. Use Default Task Spec for runs without their own, and turn on Refresh Status to bring the group status up to date.

How to integrate Parallel in automation workflow?

Parallel in three steps: start with "Watch Events", connect one credential, then add your next step.

How Parallel connects and integrates with WEXTL

Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever Parallel app is called in workflows. That allows your ai automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that Parallel supports.

Full Parallel API documentation

The following table illustrates what fields Parallel integration require during authorization flow inside our workflow builder[4].

Connect Parallel

  • API Key*Text

    ••••••••

Demonstration of Parallel connection step inside WEXTL Workflow Builder[4].
FieldTypeHelp
API KeyRequired
password

Create an API key in the platform and paste it here.

Connect Parallel to popular apps on WEXTL

Enter a name of the other app you want to sync with Parallel below. Click on selected app to explore integration options with Parallel. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.

Example automation with Parallel integration

Select Watch Events trigger from Parallel - this will be a starting point in your automation. Whenever event happens in Parallel, workflow will start[7] from Watch Events node.

Search for Add an Enrichment to a FindAll Run, connect it as the next step of integration sequence. You can use filters between Watch Events and Add an Enrichment to a FindAll Run, so only important data pass from Watch Events to the next step. WEXTL gives you full control over the process of Parallel automation. All parts of workflow are visible on the canvas[4].

Parallel on WEXTL has 37 modules for combining ai automations. Explore Parallel documentation for more.

  • ParallelWatch Events
  • DocsBotPerforms action

OR

  • DocsBotTriggers
  • ParallelAdd an Enrichment to a FindAll Run
Demonstration of how visual Parallel automation[6] looks in WEXTL.

Frequently asked questions

Common questions about automating Parallel in your workflows.

What triggers does Parallel support?

Parallel has 1 trigger, including "Watch Events". Triggers are start points of the workflow, and automations may start from them.

What actions can I run in Parallel?

Integration has 36 actions, including "Get a FindAll Run", "Get a FindAll Run Result", and "Get a FindAll Run Schema", and more. Refer to our Parallel Documentation for detailed inputs and outputs.

Do I need to write code to build automations?

No. The 36 Parallel modules, like "Get a FindAll Run", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].

Is the integration secure?

Yes. You fill in the Parallel credential once. WEXTL encrypts it at rest, and only your team can use it.

How does WEXTL integrate with Parallel?

Through the official Parallel API: 36 modules, plus "Make an API Call" for any endpoint they don't cover[3].

Can I use webhooks with Parallel?

Yes. "Watch Events" is instant: Parallel pushes each event, so there is no polling delay.

Why use WEXTL platform for Parallel automation?

WEXTL is an AI-first visual canvas: describe the Parallel flow in plain words and AI wires the nodes[4].

Automate Parallel on WEXTL®

Claim your 3-day trial to build Parallel integrations and access every WEXTL® feature.

Cancel anytime.

References

List of sources used to gather information about the Parallel integration.

  1. Parallel integration source code, module specs and credentials implementation.
  2. Internal Parallel integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official Parallel vendor API documentation, 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. WEXTL® Apps Library
  6. WEXTL® Parallel App Documentation
  7. WEXTL® Workflow Scheduler
  8. WEXTL® HTTP node documentation

How we write and maintain Parallel app documentation

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