How to Export Your Trigify Data Before October 22

TL;DR

Don't treat this as a single CSV export. Before your Trigify access ends, preserve four things: your monitoring sources, your qualification logic, your downstream integrations and your historical results.
Saved searches and some configuration can be retrieved through Trigify's API or MCP server. Workflow results can be exported as CSVs. Watchlists, prompts, conditions and other configuration may require manual capture.
Start with the configuration you'll need to rebuild active workflows, then preserve the historical results you want for reference. Inventory every workflow and integration so nothing stops unexpectedly at cutover.
For customers on Trigify's standard notice period, access ends on October 22, 2026. Follow the date in your own account notice if it differs.

Trigify is retiring its standalone platform as its team joins HubSpot. SignalRaven is independent of both companies. Trigify's notice and support team are the official route, and the inventory below works with any next tool.

Don't just save the results. Save how your system works

A Trigify customer's first instinct is to export the results. The more valuable asset is usually the logic behind them: what you monitored, who you wanted to find, how you decided what mattered and where the resulting signals went. Capture the configuration first. Your next tool needs it on day one, and past results become an archive you'll mostly read.

Before you lose access, preserve, roughly in this order:

What you monitor. People, companies, keywords, Boolean searches, watchlists.
How you qualify it. Prompts, conditions, ICP rules, severity and signal configuration.
Where signals go. CRM, Slack, Sheets, Clay, webhooks, sequencers and scripts.
Historical results. CSV exports and run history.

Historical results are useful, but your configuration is what lets you recreate the system.

Your deadline and Trigify's support contact

For customers on the standard notice period, Trigify's announcement says access ends at 11:59pm BST on October 22, 2026, and that integrations, API access, monitoring and signal collection stop then. Other contracts follow their account-specific notice. Treat the date in your notice as an absolute deadline, not your migration date. Export and test your replacement before it.

Can't export something yourself? Ask now.

Trigify's FAQ points to its in-app export options and to the Contact Support link on its announcement page, and replying to your customer notice reaches the same team. Trigify asks customers to raise export needs early. Ask for your full run history, your Social Signals target lists and any Agent Memory table missing from your workspace.

What each Trigify export route covers

Trigify's help center documents CSV export one workflow at a time. No route covers everything, so combine them.

Route	What it saves	What you'll still need to capture
Output tab CSV	Runs on the loaded page, in columns you pick	Other pages, loop rows, nested sub-tables
Google Sheets action	New runs until integrations stop	Past runs
MCP server	Saved searches and profile monitors	Social Signals and workflows (outside its documented tools)
REST API	Searches, Social Signals targets, workflow JSON, run history	Agent Memory tables (it lists names only)
By hand	Prompts, If conditions, signal settings	Anything you skip

Where possible, preserve both the machine-readable configuration and a human-readable copy: a search record and a screenshot of its Query Preview, a workflow export and the pasted prompt text, a watchlist export and a one-line description of what it was for. APIs and schemas change. The human-readable copy is what tells you what the search was supposed to do.

1. Inventory everything you still use

Start the worksheet first, then fill it as you work through the steps below. Give every search, monitor, watchlist, workflow and downstream system a row. Long URL lists get their own tab. The examples are fictional.

Item	Type	Source	Qualification	Destination	Owner
Payroll switching	Keyword or Boolean saved search	OR "switching payroll", "payroll migration"; NOT "hiring"; every 12h	See the "Qualify commenters" workflow	Feeds "Qualify commenters"	RevOps lead
Main competitor's page	Monitored company page	Page URL; daily	HIGH if title mentions payroll	CRM task via HTTP Request	SDR lead
Top 150 contacts	Social Signals watchlist	URL tab; liked competitor content; daily	Named list	Slack channel	Account owner
Qualify commenters	Workflow	Payroll switching	Prompt; If company size over 200; HIGH	Clay webhook table, Google Sheet	GTM engineer
Q2 webinar buzz	Keyword or Boolean saved search	OR "payroll webinar"; weekly	None	Slack channel	Marketing lead
Payroll chatter off LinkedIn	Keyword search on another network	OR "payroll software"; weekly	None	Slack channel	Marketing lead

Step 6 adds the decision columns.

2. Preserve your sources

Sources are the searches, monitored profiles, company pages and Social Signals lists that tell Trigify where to look.

Saved searches and profile monitors. Screenshot each keyword search's Query Preview, and confirm every person and company monitor has a profile URL. Then pull the records through one of the routes below.

Social Signals watchlists. Start with the original CSV you uploaded. Trigify's help center documents upload only. If the file's gone, open Manage profiles or Edit signals from the feed header to see the pre-filled setup. Record each watchlist's signal types, inputs and cadence.

If you'd rather not touch the API, the UI, CSV export and a manual inventory cover most setups, and Trigify support can supply anything inaccessible. The two options below are for teams comfortable with technical tools. Endpoints and help-center pages were rechecked on September 25, 2026, and Trigify's documentation may change during the shutdown.

Option 1: Use Trigify's MCP server

Connect an MCP-capable AI assistant to https://api.trigify.io/mcp and sign in with your Trigify login. Have it run list_searches, then get_search on each search, and put the results in one table. Both tools are credit-free.

Option 2: Use the REST API

Create a key in Settings under API Keys and send it in the x-api-key header. Settings also links the API reference, and the raw OpenAPI spec lives at api.trigify.io/docs.

GET /v1/searches returns the index only: ID, name, status, type, dates and result count. Page through with the cursor and check the total against the app.
GET /v1/searches/{id} holds the query: keywords (the OR list), keywords_and, keywords_not and profile_url, plus frequency, time frame, job titles and other filters. Call it once per search.
GET /v1/searches/{id}/results returns posts. Engagers from saved searches live in your workflow outputs.
GET /v1/social-signals/subscriptions returns each watchlist target's LinkedIn URL and configuration.
On Enterprise, topic searches and bulk-tracked profiles return engagers from GET /v1/topics/{id}/engagements and POST /v1/profile/engagement/results.

3. Preserve your qualification logic

This is the part a CSV never captures, and the part your next tool needs most.

General Agent prompts. Copy every General Agent prompt word for word with its output format. Don't rewrite or clean them up during export. Preserve the original first and optimize later, or you'll lose the configuration that was actually running.

If conditions. Record each If Condition as variable, operator and value, and note which conditions share a node, since all of them must pass. For example: Condition: company_size. Operator: greater than. Value: 200. Relationship: AND with the title condition.

Signal settings. Record each Configure Signal node's name, severity and category.

Workflow JSON. Save each workflow's GET /v1/workflows/{id} response as a backup. Its fields are undocumented, so your pasted prompts stay the primary copy.

Redact credentials before anything leaves the workspace.

Trigify warns against sharing workflows that contain hardcoded API keys. Before sharing exported workflow JSON or screenshots, remove API keys, authorization headers, webhook secrets and other credentials.

4. Preserve your destinations and dependencies

Exporting your data is only half the migration. Every system expecting data from Trigify needs a replacement feed or an intentional shutdown, and many migrations fail because a downstream dependency silently stops receiving information.

Outbound: integration nodes (CRM, sequencer, Slack, Google Sheets, Notion) and HTTP Request receivers such as Clay webhook tables. Search records omit any webhook_url set through the API, so check the scripts that created your searches.
Inbound: anything that posts to a Webhook Trigger URL. Trigify's own example is a CRM event that creates a saved search.
Keyed to Trigify: CRM properties and workflows built on Trigify fields or severity labels, sequencer campaigns it fills, and scripts that call the API, MCP server or CLI.

Cross-check with GET /v1/integrations. Give each consumer its own row with at least these fields: System, Direction, Owner, Data received or sent, Matching key, Replacement, Tested.

5. Export your historical results

This step comes after configuration on purpose. Results are evidence for the side-by-side test, not the system itself.

Open the workflow and switch to the Output tab. In the footer, turn off auto-refresh and set 100 rows per page.
Click a step's cell, then click Add as column on each field you need: LinkedIn profile URL, name, company, post URL and the agent's verdict.
Click Export CSV, pick your columns and download.
Step to the next page and repeat. Trigify names every file {workflow-slug}-outputs-{date}.csv. Add the page number to each file name.

For an array of people or signal results, open it in the detail panel, choose Map to Table and export that sub-table separately. For loop rows and long histories, a script can page through GET /v1/workflows/{id}/executions and pull each run's step outputs.

Treat the LinkedIn profile URL as your primary person-level matching key during migration. Keep that column in every file. It matches a person across files, and SignalRaven signals carry it too.

If you want a simple rolling backup during the transition, you can add a Google Sheets Append Row action (2 credits per action) to workflows you'll run until cutover. New rows land in your own Google account and can feed the side-by-side run. Reprocessing a large backlog can burn through credits quickly, so use CSV for history.

Workflows belong to an organization. If you're in more than one, switch to each and repeat these steps.

6. Decide what to archive, rebuild, retire or replace elsewhere

A shutdown is also an opportunity to clean up the system. Don't recreate every search and workflow simply because it exists. Look at the last useful result, the current owner and the downstream use before deciding what deserves to move.

Item	Last useful result	Backup	Replacement	Test status	Decision
Payroll switching	Sep 24	Search record, screenshot	Keyword source in the next tool	Compare signals side by side	Rebuild
Main competitor's page	Sep 23	Search record	Company page source	Compare signals side by side	Rebuild
Top 150 contacts	Sep 22	Original CSV	Followed-people source	Compare signals side by side	Rebuild
Qualify commenters	Sep 24	Workflow JSON, CSVs	ICP qualification in the next tool; pause "Payroll Q4" at cutover	In progress	Rebuild
Q2 webinar buzz	Jun 30	Search record	None	Skip	Retire
Payroll chatter off LinkedIn	Sep 20	Search record	Separate tool for that network	Not started	Replace elsewhere

Archive. Historical data worth retaining for reference.
Rebuild. Active sources and rules that consistently produced useful signals.
Retire. Quiet searches, duplicate monitors and anything nobody owns.
Replace elsewhere. Functionality your chosen replacement doesn't cover.

Rebuild the logic that matters, not the architecture Trigify happened to use.

7. If you're moving to SignalRaven, translate the intent, not the nodes

A Trigify workflow might chain a search, engagement collection, an AI prompt, an If condition, a severity setting and a destination. Don't try to rebuild that node for node. Use the inventory to preserve what each workflow was trying to accomplish, then express it in SignalRaven's model: sources, ICP qualification with built-in filtering, urgency and destinations.

Trigify	SignalRaven
Source: competitor company page	Source: a company's LinkedIn page
Workflow: collect engagers	Built into every source
Agent prompt: does this person fit a finance ICP?	ICP: title and role, market affinity, industry, company size and location, each with its own threshold
If: company has more than 500 employees	ICP: company size range
Severity: HIGH if senior title	Urgency from 1 to 10, with signal history from the person and company
Destination: Clay webhook	Destination: Clay directly, or a signed webhook into n8n, Zapier or Make

A prompt and several If conditions may translate into ICP settings. A monitored company page becomes a company source. A severity rule maps to the urgency model. A webhook or Slack destination is recreated downstream. Preserve the original configuration first, then translate it. The migration playbook reads the inventory column by column, and if you're still choosing a tool, read whether SignalRaven fits as a Trigify alternative.

8. Run both systems side by side

Keep Trigify running on your proven sources while the replacement runs on the same ones. Log every signal from both in one sheet, dedupe on the LinkedIn profile URL and read through the people only one tool kept. That's where qualification differences show, and it's the reason to export the historical results at all.

Trigify data export FAQ

What should I export first?

Active sources, qualification logic and integration configuration. Those are what you'll need to keep workflows running. Export historical results after you've preserved the setup.

Do I need to migrate every Trigify workflow?

No. Use the inventory to identify what's active, what produced useful signals recently and what still has an owner. Archive or retire the rest.

Can I export all my Trigify data at once?

No account-wide export is documented. Contact Trigify's support team now about anything you can't pull yourself, then combine Output tab CSVs, MCP or API pulls and hand copies.

How long do I have to export my Trigify data?

Until your access ends: 11:59pm BST on October 22 on the standard notice period, or the date in your account notice. With no published deletion date, treat your end date as the deadline.

Can SignalRaven import my Trigify workflows directly?

Not as Trigify workflow files. The useful pieces, your sources, ICP logic and destinations, can be translated into SignalRaven's model, and LinkedIn URLs for people and companies paste in as sources in batches.

Who do I contact at Trigify about exporting my data?

Use the Contact Support link on Trigify's announcement page, or reply to your customer notice.

Start free trial →