Zapier Integration

This guide shows how to add FlautoPsy webhook monitoring to Zapier Zaps.

Step 1: Get Your Webhook URL

  1. Log in to FlautoPsy at https://flautopsy.stralocroft.com/dashboard
  2. Go to Settings → Setup (or /setup)
  3. Copy your unique webhook URL

Step 2: Add a Webhooks by Zapier Step

  1. Open your Zapier Zap (or create a new one)
  2. Click + to add an action step
  3. Search for Webhooks by Zapier and select it
  4. Choose Catch Hook (if setting up webhook trigger) or POST (if sending data to FlautoPsy)
  5. Select POST

Step 3: Configure the Webhook

URL

Paste your FlautoPsy webhook URL from Step 1

Payload Type

Select JSON from the dropdown

Data

Click Show Options and then Payload to enter the JSON body.

Paste this template:

json
{
  "workflow_id": "your-workflow-name",
  "prompt": "promptContent",
  "output": "outputContent",
  "latency_ms": 250,
  "cost_tokens": 1500,
  "model": "gpt-4"
}

Step 4: Map Zapier Fields

Replace the template values with actual Zapier variables:

  • Click on a field (e.g.,
    text
    promptContent
    )
  • Select the data from your LLM step from the Insert Data dropdown
  • Repeat for each field

Example Mapping

If you're using OpenAI in Zapier:

json
{
  "workflow_id": "email-processor",
  "prompt": "{{prompt_from_openai}}",
  "output": "{{text_from_openai}}",
  "latency_ms": 300,
  "cost_tokens": {{usage_tokens_from_openai}},
  "model": "gpt-4"
}

The exact field names depend on your LLM step. Check the LLM action's output fields.

Step 5: Test the Webhook

  1. Click Continue
  2. Run a test of your Zap
  3. Go to FlautoPsy dashboard → Traces to verify the trace arrived
  4. If no trace appears, check:
    • The webhook URL is exactly correct
    • The JSON is valid (use a JSON validator)
    • All required fields are present

Step 6: Turn On Your Zap

  1. Click Publish to activate your Zap
  2. Run your Zap 10+ times to build a baseline
  3. Traces will appear in FlautoPsy after each execution

Zapier-Specific Tips

  • Zapier's LLM integrations vary (OpenAI, Claude, etc.) — check your LLM action's output field names
  • Use
    text
    {{field_name}}
    syntax for variable mapping, not
    text
    ${}
    or
    text
    {{}}
  • Test your webhook by running the Zap once before publishing
  • Zapier automatically sends
    text
    Content-Type: application/json

Common Issues

"Invalid URL" Error

  • Copy your webhook URL again from FlautoPsy Settings
  • Ensure no extra spaces or special characters

"Webhook failed: 400 Bad Request"

  • Check that all fields in the JSON are correctly mapped
  • Ensure
    text
    latency_ms
    and
    text
    cost_tokens
    are numbers, not strings
  • Verify the JSON is valid (no trailing commas, proper quotes)

Data Not Mapping Correctly

  • Use the Insert Data dropdown to select fields from your LLM action
  • Don't manually type field names — always use the dropdown
  • If a field doesn't appear in the dropdown, it may not be available from that action

Troubleshooting

My Zap runs but traces don't show in FlautoPsy

  • Check the Zap execution history to see if the webhook step succeeded
  • Go to FlautoPsy → Dashboard → Traces (may take 5-10 seconds)
  • If still missing, create a test Zap with the same webhook to isolate the issue

How do I monitor multiple Zaps?

  • Use different
    text
    workflow_id
    values for each Zap
  • Or use the same
    text
    workflow_id
    to group related Zaps together

Can I send custom fields?

  • Currently, FlautoPsy only processes the 6 core fields (workflow_id, prompt, output, latency_ms, cost_tokens, model)
  • Extra fields in the JSON are ignored
  • Contact support@stralocroft.com if you need custom fields

Next Steps