Skip to main content

Step 6: Set Up Triggers

Time to complete: ~2 minutes
What you'll do: Configure how to start document generation
What you'll need: Understanding of your preferred trigger method (manual, button, webhook, or API)

Triggers are the "go button" that tells Gdocify to generate documents. They determine when and how your automation runs.

UI Navigation

Where to find it: Click the "Execute Automation" or "Triggers" button, typically found in the bottom-left area or in the "More Options" menu.

What Are Triggers?​

Triggers are different ways to start your automation:

  • Manual trigger: Click a button in Gdocify
  • Airtable button: Click a button in your Airtable base
  • Webhook: Call a URL from another app
  • API: Send a request from your own application

Opening Trigger Configuration​

  1. Click the "Execute Automation" or "Triggers" button (bottom-left or in settings)
  2. You'll see different trigger options based on your data source

Manual Triggers​

The simplest way to run your automation:

  1. Go to your automation in Gdocify
  2. Click the "Run" or "Generate" button
  3. Select which records to process (all records or specific ones)
  4. Click "Generate"

This is great for testing or one-time generation.

Airtable Button Trigger​

If you're using Airtable, you can add a button directly in your base:

  1. In Airtable, add a "Button" field to your table
  2. Configure the button to call the Gdocify webhook URL
  3. When you click the button, it generates a document for that specific record

This is perfect for on-demand generation from Airtable.

Webhook Triggers​

Webhooks let other apps trigger your automation:

  1. Copy the webhook URL from Gdocify
  2. Configure it in your other app (Zapier, Make, etc.)
  3. When the webhook is called, Gdocify generates documents

Useful for integrating with other automation tools.

API Triggers​

For developers, you can trigger via API:

  1. Get your API endpoint and authentication key
  2. Send a POST request with the record data
  3. Gdocify processes the request and generates documents

Perfect for custom integrations.

Testing Your Trigger​

Before generating documents for all records:

  1. Test with a single record first
  2. Verify the document is generated correctly
  3. Check that it's saved in the right location
  4. Once confirmed, run for all records

What Happens Next?​

With triggers set up, you're ready to generate your first document! Continue to Step 7: Generate Your First Document.

Tips​

  • Start with manual triggers: Easiest way to test your automation
  • Test before scaling: Always test with one record before running for hundreds
  • Use appropriate triggers: Choose the trigger type that fits your workflow
  • Document your triggers: Note which trigger you're using for future reference

Common Issues​

  • "Trigger not working": Check that you've copied the URL correctly
  • "Permission denied": Verify authentication credentials
  • "No records found": Make sure your data source has records and they're accessible