Hi @bartosz1991,

Hey there! Welcome to the community. Let's walk through the revamped instructions to make things crystal clear:

First things first, the trigger gets things rolling for the Zap. The trigger is when a new blog post pops up on your WordPress site. So, go ahead and pick WordPress as the trigger app and select "New Post" as the trigger event. After that, pick out your WordPress account and site.

Now, let's talk about the action - that's what the Zap does after the trigger. In this case, it's all about shooting off an email through ActiveCampaign. Just choose ActiveCampaign as the action app and choose "Create Campaign" as the event. Remember to select your ActiveCampaign account.

Next, you'll want to fill in the campaign details. Regarding the "Type," go with "Standard." Then, give your campaign a catchy name in the "Name" field. For the "List," pick the mailing list where you want your email to land.

Get creative in the "HTML" field when designing your email. To include the new blog post link, use the "Post Permalink" variable from the trigger data. It'll automatically swap in the URL of the new blog post when the email is sent.

Last but not least, give your Zap a test run to double-check that everything's spot on.
 

Unfortunately, my problem has not been solved because I know how to do it myself. 

Another thing is the fact that I do not have a "TYPE" field in Active Campaign, only an "Email Message" field where I choose a template. 

And how do I know what Permalink is? It is downloaded in the trigger, but how should I save it? 

Can I ask for a little more detailed instructions?

I want the link to the post from the trigger to be transferred to the content of the email in Active Camping. How to do it? 

Because the instructions above didn't help me at all.

Hi there @bartosz1991,

It looks like your desired workflow is not possible since the ActiveCampaign “Create Campaign” action doesn’t have a field to include a link or there isn’t a way for you to customize the campaign using a Zap. However, we do have an existing feature request for this exact functionality.

I have added you to the open feature request. That does a few things:

• Bring this to the attention of the integration developers
• Help track interest in this feature being implemented
• Allows us to notify you via email if this feature becomes available in the future

While I don't have an ETA on when this feature might be implemented, we will notify you via email if it is!

Hopefully, this helps.

While waiting for your answer, I managed it myself and I managed to do it in an individual way that works.