Automatically write blog posts with Jasper and Zapier

Generative AI comes in all different varieties, and the tools you use will depend on the type of output you’re after. Jasper.ai is known for its content marketing capabilities, including its ability to spin up an entire blog post based on a few inputs. 

While you can create blog posts directly in Jasper, if you use its Zapier integration you can connect Jasper with other tools your team is using, like a project management tool and Google Docs. That way, you can keep your team organized without needing to flip back and forth between Jasper and your other tools. 

Create blog posts with Jasper and Zapier

Zapier lets you create automated workflows called Zaps, which send your information from one app to another. You can create your own Zap from scratch without any coding knowledge, but we also offer quick templates to get you started. 

If you’d like to start with a template, click on it below, and you’ll be taken to the Zap editor. You’ll need to create a Zapier account if you don’t already have one. Then, follow the directions below to set up your Zap.

You can use any project management or document tools that integrate with Zapier in this workflow, so we’ve set up a few options for you:

Before you begin

Jasper connects to Zapier via an API key, which is only available on certain Jasper plans. To generate your API key, Go to Product Settings > API tokens, then click Generate API token.

Once you have your API key, go to the My Apps section in your account menu.

Select Add a new app connection and search for Jasper.

Then paste in the API key you generated in Jasper.

You’ll also need to set up your project management or spreadsheet tool with the required inputs in Jasper. The Jasper step in your Zap will require three things: 

• Topic (1-2 sentences) 

• Tone 

• Intended audience 

Most of your project management or spreadsheet tools have custom fields. In this example, you can add the three fields you need for Jasper. Each field has a dropdown list so that anyone on the team adding content knows their options. 

The above is an example with Airtable, but you can do the same thing in tools like Monday, Google Sheets, or Asana.  

If you like, you can also add a specific field, label, or some type of indicator (like a status dropdown) that the content is intended for Jasper. You’ll only need this if you have blog post ideas that you don’t want to add to Jasper and need to make a distinction in your project management or spreadsheet tool. Here’s an example with Google Sheets: 

Set up your trigger step

Every Zap consists of a trigger step and one or more action steps. When you publish your Zap, it will run the action steps every time the trigger event occurs. 

Your Zapier trigger will be different based on your project management tool but driven by the field you’ve created to designate the content should be sent to Jasper. The trigger might be “New Record”, “Status is {whatever you’ve set up}”, or “Column Value Changed in Board”.

Here’s an example with Airtable: 

You’ll also need to connect your trigger app’s account to Zapier, if you haven’t already.

Next, select the appropriate project or dataset, and limit to the view or filter that’s focused on records intended for Jasper. This will ensure that only new records in this specific view trigger your Zap, based on the designated status or criteria, instead of every new record added to your project management or spreadsheet tool. Here’s an example with Asana:

Next, test your trigger step. The information gathered in this test will be used to set up the rest of your Zap. Once you’re happy with the test results, click Continue to set up your first action step.

Set up your Jasper action step

For your first action step, select Jasper for the action app and Create a Blog Post for the action event.

Connect the Jasper account you previously connected when you added your API key. If you skipped that step, you can connect your Jasper account now and paste in the API key in the Zap editor.

Next, you need to map the fields from your project management tool for Topic, Tone, and Intended Audience by clicking the + icon next to each field and selecting the appropriate data for each from the list of options.

Test your action step, then click Continue.

Send your blog post to another app

Jasper will generate the blog post directly in Zapier so you’ll still need to send that output somewhere. 

For example, you might want to add it to a Google Doc (or a Google Drive folder) so you can edit it from there directly. Or perhaps you want to save yourself time and add it straight to WordPress or back to your project management tool if that’s where you work.  

In those cases, the action might be “Append Text to Document,” “Create New Blog Post,” or “Create Record.” 

Here’s an example with Google Docs: 

Next, configure the content by adding Jasper’s text output along with any relevant fields from your project management or spreadsheet tool that you’d like to include. For example, you could use the title field as the document name and add additional details like the assigned team member or due date within the content. 

To pull in data from your previous steps, simply click the + icon inside each relevant field and choose the appropriate data from the options. Here’s an example with Google Drive:

Test your action step to make sure everything is set up correctly. If you used Google Drive or Google Docs as your final action app, it will look something like this:

If you added it back to your project management tool, it might look something like this:

Once everything looks right, you’re ready to use your Zap.

Automation will save your team time

If you’re already using Jasper to generate blog posts, you’re probably storing your planned content in one tool and then taking those ideas and turning them into Jasper prompts. By using Zapier, you’ll save time on the back-and-forth, plus keep your team more organized. You can also easily make edits to the output in Google Docs, rather than editing the doc in Jasper and then transferring the content elsewhere.

This article was originally published in August 2023. It was most recently updated in November 2024 by Elena Alston.