Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Exa

AI-powered search and content extraction from the web.

CategoryArtificial Intelligence
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Exa with Flows360

AI-powered search and content extraction from the web.

Use the Exa connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and no declared triggers.

Available actions

  • Get Contents
  • Ask AI
  • Perform Search
  • Find Similar Links
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Exa
  • Package: @activepieces/piece-exa@0.2.0
  • Exact artifact digest: sha256:f3972b3a97e12085cc13fbda9b03b0ee122f8ffa031cd5f673def4056128d969
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Get Contents (get_contents), Retrieve clean HTML content from specified URLs. Classification: read.
  • Ask AI (generate_answer), Provides direct answers to queries by summarizing results. Classification: read.
  • Perform Search (perform_search), Search the web using semantic or keyword-based search. Classification: read.
  • Find Similar Links (find_similar_links), Find pages similar to a given URL. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects5
Supported actions5
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Get Contents Yes No Retrieve clean HTML content from specified URLs.
Ask AI Yes No Provides direct answers to queries by summarizing results.
Perform Search Yes No Search the web using semantic or keyword-based search.
Find Similar Links Yes No Find pages similar to a given URL.
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Get Contents · Read

Retrieve clean HTML content from specified URLs.

get_contents · Risk: low · Retry: safe

Inputs

  • urls · array · Required, Array of URLs to crawl
  • text · boolean · Optional, If true, returns full page text. If false, disables text return.
  • livecrawl · string · Optional, Options for livecrawling pages.
  • livecrawlTimeout · number · Optional, Timeout for livecrawling in milliseconds.
  • subpages · number · Optional, Number of subpages to crawl.
  • subpageTarget · string · Optional, Keyword(s) to find specific subpages.
Ask AI · Read

Provides direct answers to queries by summarizing results.

generate_answer · Risk: low · Retry: safe

Inputs

  • query · string · Required, Ask a question to get summarized answers from the web.
  • text · boolean · Optional, If true, includes full text content from the search results
  • model · string · Required, Choose the Exa model to use for the answer.
Perform Search · Read

Search the web using semantic or keyword-based search.

perform_search · Risk: low · Retry: safe

Inputs

  • query · string · Required, Search query to find related articles and data.
  • type · string · Optional, Type of search to perform.
  • category · string · Optional, Category of data to focus the search on.
  • numResults · number · Optional, Number of results to return (max 100).
  • includeDomains · array · Optional, Limit results to only these domains.
  • excludeDomains · array · Optional, Exclude results from these domains.
  • startCrawlDate · string · Optional, Only include results crawled after this ISO date.
  • endCrawlDate · string · Optional, Only include results crawled before this ISO date.
  • startPublishedDate · string · Optional, Only include results published after this ISO date.
  • endPublishedDate · string · Optional, Only include results published before this ISO date.
  • includeText · array · Optional, Strings that must be present in the text of results.
  • excludeText · array · Optional, Strings that must not be present in the text of results.
Find Similar Links · Read

Find pages similar to a given URL.

find_similar_links · Risk: low · Retry: safe

Inputs

  • url · string · Required, Reference URL to find semantically similar links.
  • numResults · number · Optional, Number of results to return (max 100).
  • includeDomains · array · Optional, List of domains to include in results.
  • excludeDomains · array · Optional, List of domains to exclude from results.
  • startCrawlDate · string · Optional, Include links crawled after this date (ISO format).
  • endCrawlDate · string · Optional, Include links crawled before this date (ISO format).
  • startPublishedDate · string · Optional, Only include links published after this date (ISO format).
  • endPublishedDate · string · Optional, Only include links published before this date (ISO format).
  • includeText · array · Optional, Strings that must be present in the webpage text (max 1 string of up to 5 words).
  • excludeText · array · Optional, Strings that must not be present in the webpage text (max 1 string of up to 5 words).
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the Exa connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-exa@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Exa connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-exa@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com