Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Foreplay

Competitive advertising data and creative insights platform. Search, filter, and analyze ads and brands with live and historical ad creatives, metadata, and competitive intelligence.

CategoryMarketing
Authenticationcustom
Version0.1.8
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Foreplay with Flows360

Competitive advertising data and creative insights platform. Search, filter, and analyze ads and brands with live and historical ad creatives, metadata, and competitive intelligence.

Use the Foreplay 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 3 triggers.

Available actions

  • Get Ad by ID
  • Get Ads by Page
  • Find Brands
  • Find Ads
  • Find Boards

Available triggers

  • New Ad in Spyder
  • New Ad in Board
  • New Swipefile Ad

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: Foreplay
  • Package: @activepieces/piece-foreplay-co@0.1.8
  • Exact artifact digest: sha256:0ba7bccc6a1ffa305463829de5104b25e822d561f6d3f274e19b0fb44f3d6c81
  • 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 Ad by ID (getAdById), Get detailed information about a specific ad by its ID. Classification: read.
  • Get Ads by Page (getAdsByPage), Get all ads for a Facebook Page ID with filtering and pagination. Classification: read.
  • Find Brands (findBrands), Search for brands by name with fuzzy matching. Classification: read.
  • Find Ads (findAds), Search and filter ads by text, dates, platforms, and categories. Classification: read.
  • Find Boards (findBoards), Get all boards for the authenticated user with pagination. Classification: read.

Trigger contracts

  • New Ad in Spyder, polling.
  • New Ad in Board, polling.
  • New Swipefile Ad, polling.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects8
Supported actionsNot published
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Get Ad by ID Yes No Get detailed information about a specific ad by its ID.
Get Ads by Page Yes No Get all ads for a Facebook Page ID with filtering and pagination.
Find Brands Yes No Search for brands by name with fuzzy matching.
Find Ads Yes No Search and filter ads by text, dates, platforms, and categories.
Find Boards Yes No Get all boards for the authenticated user with pagination.
New Ad in Spyder Yes No polling trigger declared by the pinned package.
New Ad in Board Yes No polling trigger declared by the pinned package.
New Swipefile Ad Yes No polling trigger declared by the pinned package.

Triggers

New Ad in Spyder · Poll

Triggers when new ads are added for a brand in Spyder.

Inputs

  • brand_id · string
  • polling_interval · number
  • live · string
  • display_format · array
  • publisher_platform · array
  • niches · array
  • market_target · array
  • languages · array
New Ad in Board · Poll

Triggers when a new ad is added to the selected board.

Inputs

  • board_id · string
  • polling_interval · number
  • live · string
  • display_format · array
  • publisher_platform · array
  • niches · array
  • market_target · array
  • languages · array
New Swipefile Ad · Poll

Triggers when a new ad is added to your swipefile collection.

Inputs

  • polling_interval · number
  • start_date · string
  • end_date · string
  • live · string
  • display_format · array
  • publisher_platform · array
  • niches · array
  • market_target · array
  • languages · array

Setup

Setup

  1. Add the Foreplay 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-foreplay-co@0.1.8; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 3 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Foreplay 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-foreplay-co@0.1.8 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