Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Xquik

Search public X/Twitter posts, users, timelines, and trends for automation workflows.

CategoryBusiness Intelligence
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Xquik with Flows360

Search public X/Twitter posts, users, timelines, and trends for automation workflows.

Use the Xquik 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 7 actions and no declared triggers.

Available actions

  • Search Tweets
  • Get Tweet
  • Search Users
  • Get User
  • Get User Tweets
  • Get Trends
  • 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: Xquik
  • Package: @activepieces/piece-xquik@0.1.0
  • Exact artifact digest: sha256:dfd325bf0a4a68eb6a0c588ade178aed88d974a900e1081432c62610b386bb36
  • 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

  • Search Tweets (search_tweets), Search public X/Twitter posts with X query operators. Classification: read.
  • Get Tweet (get_tweet), Look up a public X/Twitter post by ID Classification: read.
  • Search Users (search_users), Search public X/Twitter users by name or username. Classification: read.
  • Get User (get_user), Look up a public X/Twitter user by username or user ID Classification: read.
  • Get User Tweets (get_user_tweets), List recent posts from a public X/Twitter user Classification: read.
  • Get Trends (get_trends), Get X/Twitter trending topics by region 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 objects7
Supported actions7
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Xquik API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Search Tweets Yes No Search public X/Twitter posts with X query operators.
Get Tweet Yes No Look up a public X/Twitter post by ID
Search Users Yes No Search public X/Twitter users by name or username.
Get User Yes No Look up a public X/Twitter user by username or user ID
Get User Tweets Yes No List recent posts from a public X/Twitter user
Get Trends Yes No Get X/Twitter trending topics by region
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Search Tweets · Read

Search public X/Twitter posts with X query operators.

search_tweets · Risk: low · Retry: safe

Inputs

  • query · string · Required, Search query. Supports keywords, hashtags, from:user, exact phrases, and X search operators.
  • queryType · string · Optional, Return latest posts or top engagement-ranked posts.
  • limit · number · Optional, Maximum posts to return. Use 1-200.
  • cursor · string · Optional, Pagination cursor from a previous response.
  • sinceTime · string · Optional, Only return posts after this ISO timestamp.
  • untilTime · string · Optional, Only return posts before this ISO timestamp.
Get Tweet · Read

Look up a public X/Twitter post by ID

get_tweet · Risk: low · Retry: safe

Inputs

  • tweetId · string · Required, Numeric X/Twitter post ID.
Search Users · Read

Search public X/Twitter users by name or username.

search_users · Risk: low · Retry: safe

Inputs

  • query · string · Required, Name, username, brand, or keyword to search for.
  • cursor · string · Optional, Pagination cursor from a previous response.
Get User · Read

Look up a public X/Twitter user by username or user ID

get_user · Risk: low · Retry: safe

Inputs

  • user · string · Required, Username with or without @, or a numeric user ID.
Get User Tweets · Read

List recent posts from a public X/Twitter user

get_user_tweets · Risk: low · Retry: safe

Inputs

  • user · string · Required, Username with or without @, or a numeric user ID.
  • cursor · string · Optional, Pagination cursor from a previous response.
  • includeReplies · boolean · Optional, Include reply posts in the timeline response.
  • includeParentTweet · boolean · Optional, Include parent post context when available.
Get Trends · Read

Get X/Twitter trending topics by region

get_trends · Risk: low · Retry: safe

Inputs

  • woeid · number · Optional, Yahoo Where On Earth ID. Use 1 for worldwide, 23424977 for US, 23424975 for UK, or 23424969 for Turkey.
  • count · number · Optional, Number of trends to return. Use 1-50.
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 Xquik 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-xquik@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 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 Xquik 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-xquik@0.1.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