Zapier Integration

Zapier connects SALZ to thousands of applications without code. You can build automated workflows (called Zaps) that generate text with AI, optimize it with SALZ, and send it wherever you need it.

How It Works

SALZ connects to Zapier through the Webhooks by Zapier app. You configure an HTTP request to call the SALZ optimize endpoint as an action step in your Zap.

Setting Up SALZ in Zapier

Step 1: Create a New Zap

1. Log in to Zapier and click Create Zap.
2. Choose your trigger app (e.g., Google Forms, Airtable, Gmail, or a Schedule trigger).

Step 2: Add the SALZ Action

1. For the action step, search for Webhooks by Zapier.
2. Select Custom Request as the action event.
3. Configure the request:

4. In the Data field, click in the text area and use the Zapier field picker to insert the text from your trigger step.

Step 3: Map the Response

After the SALZ action runs, the optimized text is available as optimized in subsequent steps. Map this field to your destination app.

Example Zap: AI Blog Post Pipeline

Trigger: Schedule by Zapier (runs weekly)

Action 1: OpenAI -- Generate a blog post draft based on a topic list in a spreadsheet.

Action 2: Webhooks by Zapier -- Send the generated text to SALZ for optimization.

{
  "text": "{{steps.openai.choices[0].message.content}}"
}

Action 3: WordPress -- Create a new draft post using the optimized text from {{steps.salz_webhook.optimized}}.

Example Zap: Form Response Optimizer

Trigger: Google Forms -- New form response.

Action 1: Webhooks by Zapier -- Optimize the long-text response field with SALZ.

Action 2: Gmail -- Send the optimized version back to the form respondent.

Example Zap: CMS Content Polish

Trigger: Airtable -- When a record enters the "Ready for Review" view.

Action 1: Webhooks by Zapier -- Send the draft content field to SALZ.

Action 2: Airtable -- Update the same record with the optimized text in a "Polished Content" field.

Handling Errors

Zapier will show a failed step if the SALZ API returns an error. Common issues:

• 401 error -- Check that your API key in the Headers field is correct and includes the Bearer prefix.
• 429 error -- You have hit the rate limit. Add a Delay by Zapier step (60 seconds) before the SALZ action if you are processing multiple items.
• 400 error -- The text field is empty or exceeds the character limit. Add a Filter step to skip empty text fields.

Tips

• Use Zapier Paths to handle different text types with different SALZ parameters (e.g., casual tone for social media, formal for reports).
• Test your Zap with the "Test" button at each step to verify the SALZ response before turning on the Zap.
• Store your API key in the Headers field, not in the URL. This keeps it out of Zapier logs.
• Add a Filter step before the SALZ action to skip records with empty text fields or text shorter than a minimum length.
• Use Formatter by Zapier to truncate text to 10,000 characters before sending it to SALZ if your source data might exceed the limit.
• Monitor your usage. Each Zap run that calls SALZ counts as one API call against your monthly quota. Check your SALZ dashboard to track consumption.