n8n: connect Phacet to your apps

The Phacet n8n node lets you connect Phacet to hundreds of external tools using n8n's visual workflow builder: no code required. Use it to embed Phacet into existing processes and automate multi-step workflows.

n8n chains Triggers and Actions into workflows: when something happens in one tool (a trigger), n8n performs a defined action in another: like sending new data to Phacet or reacting to updates in your workspace.

Why use it?

  • Eliminate manual exports and cross-tool copy/paste
  • Trigger Phacet Tables based on live events from other apps (e.g., "file uploaded," "form submitted")
  • Push Tables results to downstream systems automatically (e.g., "send a Slack alert when a mistake is found in an invoice")
  • Create tight feedback loops across AI, automation, and human review
  • Self-host your automation: n8n can be self-hosted, giving you full control over your data and workflows

How it works

The node uses your Phacet API key with n8n's Triggers and Actions model:

  • Trigger → Phacet: External apps send data to Tables in Phacet.
  • Phacet → Action: Tables results trigger actions in your stack.

You keep full control over access via API keys.

How to set up Phacet and n8n integration

⚙️

Only Admin users can set up the Phacet n8n connection as it requires the ability to manage API keys in Phacet.

Use Case 1: External Trigger → Action in Phacet

Automate Phacet actions when something happens in your external tool (e.g., Airtable, Salesforce, Google Drive).

1. Authentication

  • Generate an API Key in Phacet from your Settings > API keys dashboard.
  • In n8n, add a new Phacet credential and paste your API key.

2. Trigger Setup (External Tool)

  • Add a trigger node for the app and event that will start the workflow (e.g., "New Spreadsheet Row" in Google Sheets).
  • Follow n8n's setup to test and capture sample data.

3. Action Setup (Phacet)

  • Add a Phacet node and choose the action (e.g., "Create Row", "Update Row").
  • Select the target Table and Session.
  • Map fields from your trigger node to columns in your Phacet.
  • Test the node on the sample data.

4. Activate

  • Save and activate your workflow. It will now run automatically based on the trigger.

Use Case 2: Trigger from Phacet → Action in Another App

Use Phacet's native triggers directly within n8n to react to events in your Tables.

  • Add a Phacet Trigger node as the starting point of your workflow.
  • Select the trigger event.
  • Select the Table to monitor.
  • Test the trigger to validate that events are properly captured.
  • Add an action node for your target tool (e.g., send Slack message, update Google Sheet).
  • Map the values from the Phacet trigger to your target tool.
  • Test and activate.

Available Triggers & Actions

TypeEvent NameDescription
TriggerPhacet CreatedTriggers when a new Table is created.
TriggerRow Calculation CompletedTriggers when a row calculation completes successfully in a Table.
TriggerRow Calculation FailedTriggers when a row calculation fails in a Table.
TriggerRow Calculation StartedTriggers when calculations is initiated on a row in a Table.
TriggerRow CreatedTriggers when a new row is created in a Table.
ActionCreate RowCreates a row in a specific Table and Session.
ActionGet RowRetrieves a row by its ID from a specific Table. Use this after receiving a trigger to get the complete row data.
ActionUpdate RowUpdates an existing row in a specific Table with new cell values.

Business implementation examples

Below are common automation patterns you can build with Phacet and n8n — each turning manual, repetitive tasks into seamless workflows.

Use CaseExample
Email inbox sorting and routingEmails received in a shared inbox are automatically routed to a Table. The content is analyzed by AI to classify the request and assign it to the right person, with a topic label (e.g. invoice, legal, admin).
Email intake → Document extractionIncoming vendor invoices received via email are routed to a Table. Key data (supplier name, amount, VAT, due date) is extracted and structured for reconciliation.
Drive folders → Contract parsingA contract uploaded to Google Drive triggers a workflow that sends it to a Table. AI parses terms (e.g., renewal date, notice period) and updates a master legal tracker.
Invoice matching & validationA new invoice created in an ERP automatically flows into a Table. It is matched against purchase orders to flag price discrepancies or missing data.
CRM form submission → Request classificationA web form submission (e.g., vendor onboarding or budget request) triggers a workflow that sends the form to a Table. AI classifies it by topic and urgency.
Expense approval workflowsExpense reports submitted via a form are routed to a Table. AI extracts and checks values against policy thresholds, triggering alerts if needed.
Monthly report automationAt month-end, financial reports generated by an ERP are pushed into a Table for AI-based KPI extraction and summary generation, then sent to Slack or Notion.

Troubleshooting

If your workflow doesn't behave as expected:

  • Verify your API key is valid and not disabled in Phacet Settings > API Keys.
  • Check that you selected the correct Table and Session in the Phacet node.
  • Review the n8n execution log for detailed error messages.
  • Ensure your n8n instance can reach https://api.phacetlabs.com (especially if self-hosted behind a firewall).
  • For issues tied to Phacet-specific behavior, contact our Support Team.