Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.signalark.app/llms.txt

Use this file to discover all available pages before exploring further.

Play Templates are Signal Ark’s real-time signal routing layer. While GTME Plays surface strategic outreach opportunities inside the platform, Play Templates push signals out to wherever your team already works — a Slack channel, a CRM, or any system that accepts a webhook. The moment a qualifying signal is ingested, it’s evaluated against your active templates and delivered automatically. You don’t need to check Signal Ark for a template to fire. Set it up once, and it runs continuously in the background.

The 5 pre-built templates

Signal Ark ships with five ready-to-activate routing templates, each targeting a specific high-value signal pattern.

Executive Leadership Hire

Fires when a VP or C-level job posting is detected at a target account. Evaluates over a 14-day window. Use this to catch the executive change window before competitors do.

Funding Event Alert

Fires on new funding round signals. Evaluates over a 7-day window. Best routed to a #funding-alerts Slack channel for immediate rep awareness.

Competitive Co-Mention

Fires when a target account is mentioned alongside a tracked competitor in news or web content. Evaluates over a 7-day window. Ideal for displacement campaign triggers.

High Intent Keyword Match

Fires when a user-defined keyword rule matches on news or web sources. Evaluates over a 7-day window. Fully customizable — define keywords that map to your specific buyer signals.

Tech Stack Signal

Fires when a job posting at a target account mentions a competitor’s technology, indicating evaluation activity. No fixed window — fires on detection.

How routing works

When Signal Ark ingests new signals — either through real-time monitoring or scheduled data collection — all active Play Templates are evaluated automatically. Matching signals are dispatched immediately to their configured destination and logged in the Delivery Log for auditing. The routing pipeline is designed for low latency: signals typically reach their destination within seconds of ingestion.

Setting up a Play Template

1

Navigate to Play Templates

Open Plays in the left navigation, then click Templates. You’ll see the five pre-built templates with their current status (active or inactive).
2

Select a template

Click the template you want to configure. Each template shows its trigger conditions, evaluation window, and any delivery destinations already configured.
3

Choose a delivery destination

Select where matching signals should be sent:
  • Slack channel — enter the channel name (e.g., #sales-signals) using your connected Slack workspace
  • Webhook URL — paste any endpoint that accepts a POST request with JSON payload
  • CRM — push directly to HubSpot or Salesforce as a structured note (subject to CRM push guardrails)
4

Configure keyword rules (keyword templates only)

For the High Intent Keyword Match template, define your keyword list in the template settings. Enter terms that reflect your specific buyer signals — product category terms, pain point language, or technology names. Signal Ark matches against news headlines and web content.
5

Activate the template

Toggle the template to Active. It will begin evaluating all incoming signals immediately. You can pause or deactivate at any time without losing your configuration.

Delivery destinations in detail

Signals are formatted as a structured Slack message with the account name, signal type, evidence summary, and a direct link to the account in Signal Ark. Connect your Slack workspace in Settings > Integrations before activating Slack-routed templates.

Reviewing delivery history

Every template maintains a Delivery Log showing each time the template fired, which signal triggered it, the destination, and the delivery status (delivered, failed, or pending retry). Access the log from the template detail page.
Failed deliveries are retried automatically up to three times. If a webhook endpoint is consistently unreachable, the template will pause and notify the workspace admin.