Parallel and Perplexity Integration

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

Connect Parallel and Perplexity to automate ai 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 Parallel and Perplexity

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

  • Parallel

    • AI
    • 1 trigger
    • 17 searches
    • 19 actions

    Web search, page extraction and deep research for agents and workflows.[5]

  • Perplexity

    • AI
    • 1 trigger
    • 4 searches
    • 8 actions

    AI answer engine for real-time web search, Sonar chat, and embeddings.[6]

How to connect Parallel to Perplexity

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

How does the integration between Parallel and Perplexity work in WEXTL?

WEXTL exposes actions and triggers for Parallel and Perplexity 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.

Parallel triggersPerplexity actions

Parallel modules

  • 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.
  • Cancel a FindAll Run Stops a FindAll run that is still searching and marks it as cancelled.
  • Cancel a Monitor Cancels a monitor and ends its checks on the set Frequency.
  • Clear Memory Empties a whole memory scope, removing everything stored under its Memory Scope Key.
  • Create a Chat Completion Answers a conversation sent as Messages, each with a Role and Content, from a Parallel Model. Use Previous Interaction ID to continue earlier context and Max Tokens to cap the reply length.
  • Create a FindAll Run Starts a search for entities matching an Objective, an Entity Type and Match Conditions. A heavier Generator searches more thoroughly. Use Exclude List to leave out entities you already know.
  • Create a FindAll Spec from an Objective Turns a plain-language Objective into a ready FindAll spec with an Entity Type, Match Conditions and a Generator. Review it before starting a run.
  • Create a Monitor Sets up a recurring watch on the web with a Type and a Frequency. Give a Query to follow a search, or a Task Run ID to follow a run, and add a Webhook URL to be called on events.
  • Create a Response Produces an answer to the text of Input, guided by optional Instructions. Use Reasoning Effort to set how much the model thinks and Previous Response ID to carry earlier context forward.
  • Create a Task Group Opens an empty container for batching task runs, optionally tagged with Metadata. The Taskgroup Id it gets is used by the other group modules.
  • Create a Task Run Researches a question or task given as Input with the chosen Processor. Heavier tiers dig deeper. Use Include Domains or Exclude Domains to restrict sources and Output Type to shape the answer.
  • Evict from Memory Removes one task run, monitor or FindAll run from memory, by its Kind and ID. Use Memory Scope Key to act on a specific scope.
  • Extend a FindAll Run Raises the target of an earlier FindAll run by the Additional Match Limit, so it keeps searching for more matches.
  • Extract Web Page Content Reads each web page from the list of URLs and returns excerpts. Add an Objective or Search Queries to focus them, Max Characters to bound their length, and turn on Full Content or Links for more.
  • 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.
  • Make a Decision Answers up to 100 Questions about a State using researched evidence. Use Published After to ignore older sources and Include Excerpts to attach the supporting quotes to the Citations.
  • Make an API Call Sends a free-form request to the Parallel REST API, signed with your saved credential.
  • 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.
  • Trigger a Monitor Run Runs a monitor right now instead of waiting for its next scheduled check.
  • Update a Monitor Adjusts a monitor with a new Frequency, a deeper Processor or a revised Query. Use Include Domains to replace the domains it watches.
  • Watch Events Starts the workflow when Parallel posts a webhook event, with its Event Type, Timestamp and Data.

Perplexity modules

  • Cancel an Agent Response Asks Perplexity to stop an agent run started in the background. The run reports the status cancelling and stops shortly after. A run that has already ended returns an error.
  • Create a Background Agent Run Starts a Perplexity agent run that keeps going on Perplexity and returns at once with the run ID and a queued status. Read the finished answer with Get an Agent Response. Takes the same settings as Create an Agent Response.
  • Create an Agent Response Sends Input to a Perplexity agent and returns its answer once it finishes, within 3 minutes. Use Effort to set how much work the agent does, or Model or Models to pick the model yourself. Use Tools to let it search the web.
  • Create Contextualized Embeddings Turns the chunks of up to 512 documents into embeddings, with each document in its own inner array of Input. Use Dimensions to set a vector length from 128 to 1024 on the 0.6b Model.
  • Create Embeddings Converts up to 512 texts, each up to 32K tokens, into vector embeddings with the 0.6b or 4b Model. Use Encoding Format to receive the vectors as Base64 Int8 or Base64 Binary.
  • Get an Agent Response Reads one agent response by its ID. Use it to check a background run, which stays queued or in progress until it ends as completed, failed, cancelled or incomplete. A completed run carries the answer.
  • Get Computer Usage Analytics Counts computer usage per time bucket for one Dataset, from Start Time on. Use Bucket Width for daily or hourly buckets and User Email to narrow results to one member. Uses the Organization Analytics API Key when the credential has one.
  • List Models Returns the models offered by the Perplexity API, each with its ID, Created time and Owned by value.
  • Make an API Call Makes an authorized free-form request to the Perplexity REST API with your saved credential.
  • Run an Agent Sends an Input prompt to a Perplexity agent at a chosen effort and returns the answer with its Usage. Answers that take longer than 3 minutes fail. The simple version of Create an Agent Response.
  • Search Looks up a Query with the Perplexity search API and returns the Results along with a Server Time.
  • Sonar Chat Sends Messages to the Sonar model of your choice and returns the reply with its Citations, Search results and Related questions. Use Search Mode to draw on web, academic or SEC sources, and Disable Search to answer without any web search.
  • Watch Models Checks the Perplexity model list on a schedule and starts the workflow once for each model not seen before. Use Limit to adjust how many results each cycle handles.

Explore alternative integrations

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

Automate Parallel and Perplexity on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Parallel and Perplexity.

How do I connect Parallel and Perplexity?

Connect your Parallel and Perplexity 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 Parallel and Perplexity?

Example: when the "Watch Events" trigger in Parallel fires, WEXTL can "Cancel an Agent Response" in Perplexity. Parallel has 1 trigger (including Watch Events). Perplexity has 12 actions (including Cancel an Agent Response, Create a Background Agent Run, and Create an Agent Response). Add filters and transforms between steps when you need them.[1]

Can Parallel trigger actions in Perplexity, and Perplexity in Parallel?

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 Parallel and Perplexity?

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

Does Parallel integrate with Perplexity in real time?

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

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

References

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

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

How we write our apps documentation

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

Explore Parallel and Perplexity, or get started