How to trigger Zapier Zaps using axiom.ai


You can connect your automation to Zapier, pass scraped data, and access 7,000+ apps. We'll guide you through using axiom.ai's "Get data from URL" steps to post data to Zapier, setting up a Zap to receive the data, and using Zapier Formatter to extract it from an array.

Getting started


To get started, you will need the following from the axiom.ai Chrome extension:

  1. API key - The API key is found on the dashboard.
  2. Automation name - Get the name of the automation you wish to trigger.
  3. Endpoint - The current endpoint is https://lar.axiom.ai/api/v3/trigger.

Triggering a Zap using an axiom.ai automation


To get started, we are going to assume that you have an automation created.

  1. Create Zap - Create a new Zap by navigating to Zapier, and clicking "+ Create".
  2. Add trigger - Click "Trigger", then select "Webhooks by Zapier". See the section below for more information on configuring this trigger.
  3. Trigger webhook - In axiom.ai, add a Trigger webhook step to your automation. Input the URL from the "your webhook URL" section in Zapier.

Learn more about configuring the "Webhooks by Zapier" trigger:

  • Set the "trigger event" to "catch raw webhook", press continue.
  • Save the URL in the "your webhook URL" section for later.

To use data within your Zap, you'll need to first process the data:

  1. Actions - Add your actions to process the data that is being sent to the Zap, for this example, we will be using the "Formatter by Zapier" action.
  2. Configure - Follow the instructions below to configure the "Formatter by Zapier" action.

To configure the "Formatter by Zapier" step, follow the steps below:

  1. Action event - Set to "text".
  2. Transform - Set to "split text".
  3. Input - Click "+" and set to "raw body".
  4. Separator - Click into the field and set to "single speech mark".
  5. Segment index - Set to "all (as separate fields)".
  6. Continue - click continue.
  7. Test - Click "test step".
Configure the formatter by Zapier step

Testing your workflow


To test your workflow, open your axiom.ai automation and click "Run" to start the automation. Once complete, review any destinations where your data is being sent once it's been processed by Zapier. Alternatively, review your Zap runs within Zapier to confirm the zap ran.

If the desired results have not been achieved, review the Run Reports within axiom.ai, or the Zap runs section within Zapier.

Examples


Sending scraper data from an axiom.ai automation to Zapier for processing


Extracting data from a webpage and sending it to Zapier to be processed can unlock a huge amount of potential for your workflows. Learn how to get started below.

  1. Scrape - Create a new axiom.ai automation, add a scraping step. In this example, we will be using the Get data from a URL step.
  2. Trigger webhook - Following the instructions above, configure your Zap to be triggered by incoming webhooks. Add a Trigger webhook step and use the "Insert data" option to insert the [scrape-data] token.

Follow the steps from the Triggering a Zap using an axiom.ai automation to learn how to process the data that you send to your Zap.

Write data to Excel


To write data to Excel, follow the steps in Triggering a Zap using an axiom.ai automation to create your Zap. Once this has been done, head over to your Zap. After the "Formatter by Zapier" step, do the following:

  1. Excel - Search for "Microsoft Excel" and add a new step to your Zap.
  2. Action event - Set this to "Add Row".
  3. Set up - Follow the instructions in the Zap to connect your account and configure your step.
  4. Configure - To configure your data, head into the "Configure" tab. Click the "+" button beside the "Column" inputs to select your variables.

To test, trigger your automation within axiom.ai

Wrapping up


Using axiom.ai and Zapier together allows you to scrape data quickly and pass it to over 7,000 apps. With just two steps in each app (four total), you can set up a basic browser scraper to Zapier automation in minutes, which can be easily adapted to more complex use cases.