Krom Automation Pro can publish content to Facebook Pages, Twitter/X accounts, and LinkedIn automatically — triggered by any WordPress event. A new blog post goes live and Krom Automation posts it across all three platforms. A new WooCommerce product is added and Krom Automation announces it. Combined with the AI Generate Text action, you can build a fully automated content pipeline that writes and publishes social copy without any manual work.

The AI Create Post action works without social credentials configured. All other posting actions require platform-specific access tokens.

Requirements #

• Krom Automation Pro installed and activated
• Platform-specific access tokens for each social network you want to post to (see configuration below)

Configuration #

Each platform requires its own credentials. Configure all of them in Krom Automation > Settings > Social Media.

Facebook

You need a Page Access Token from the Meta Developer platform.

1. Go to developers.facebook.com and log in.
2. Click My Apps > Create App.
3. Select Business as the app type and complete the setup.
4. Add the Pages API product to your app.
5. Generate a Page Access Token for the Facebook Page you want to post to.
6. Copy the token and paste it into the Facebook field in Krom Automation > Settings > Social Media.

Screenshot: Meta Developer dashboard showing an app with the Pages API product and the Page Access Token field.

Twitter/X

You need four credentials from the Twitter Developer Portal.

1. Go to developer.twitter.com and log in.
2. Create a project and an app if you don’t already have one.
3. Under your app settings, go to Keys and Tokens.
4. Copy your API Key, API Secret, Access Token, and Access Token Secret.
5. Confirm the app has Read and Write permissions — tokens generated under read-only apps won’t be able to post.
6. Paste all four values into the corresponding fields in Krom Automation > Settings > Social Media.

Screenshot: Twitter Developer Portal Keys and Tokens page showing all four credential fields.

LinkedIn

You need an Access Token from the LinkedIn Developer platform.

1. Go to developer.linkedin.com and create an app.
2. Add the w_member_social permission scope to your app.
3. Generate an access token with that scope.
4. Paste it into the LinkedIn field in Krom Automation > Settings > Social Media.

Screenshot: Krom Automation Settings page with all three social media credential sections filled in.

Note: Social media access tokens expire periodically. If a posting action starts failing, the most likely cause is an expired token. Regenerate a fresh token from the platform’s developer portal and update it in Krom Automation settings.

Available actions #

Post to Facebook

Publishes a text message to your configured Facebook Page.

Field	Required	Description
message	Yes	The post text. Merge tags are supported.

Post to Twitter/X

Sends a tweet to your configured Twitter/X account.

Field	Required	Description
message	Yes	The tweet text. Keep under 280 characters. Merge tags are supported.

Post to LinkedIn

Shares a post on your configured LinkedIn account.

Field	Required	Description
message	Yes	The post text. Merge tags are supported.

Post to All Social

Publishes the same message to Facebook, Twitter/X, and LinkedIn simultaneously in a single action step. All three platforms must be configured for this action to succeed.

Field	Required	Description
message	Yes	The message to publish across all platforms. Merge tags are supported.

AI Create Post

Uses your configured AI provider to generate and publish a WordPress post or page based on a prompt. This action creates content on your WordPress site- it does not require social credentials.

Field	Required	Description
prompt	Yes	The prompt describing what to generate. Merge tags are supported.
post_type	No	The post type to create: post or page. Defaults to post.
post_status	No	The status to set on the created post: draft or publish. Defaults to draft.

Store Social Content

Saves platform-specific social copy as post meta on a WordPress post. Useful for a review-before-publishing workflow where you want to generate and store social copy automatically but publish it manually after review.

Field	Required	Description
post_id	Yes	The WordPress post ID to store the meta on. Use {{post_id}} from a post trigger.
tweet	No	Twitter/X copy. Merge tags supported.
facebook_text	No	Facebook post copy. Merge tags supported.
linkedin_text	No	LinkedIn post copy. Merge tags supported.

Update Post Status

Changes the status of an existing WordPress post.

Field	Required	Description
post_id	Yes	The post ID to update.
new_status	Yes	Target status: publish, draft, pending, trash, etc.

Setting up a social posting workflow #

Option 1: Fully automated — post immediately on publish

1. Go to Krom Automation > Workflows and click Add New Workflow.
2. Click Add Trigger and select Post Published.
3. Click + and add an AI Generate Text action. Write a prompt like: Write a tweet, a Facebook post, and a LinkedIn post for this article: {{post_title}} — {{post_excerpt}}. Keep each within platform character limits. Set the output key to social_copy.
4. Add a Post to All Social action using {{social_copy}} as the message.
5. Simulate to confirm the AI output looks correct.
6. Activate the workflow.

Screenshot: Canvas showing Post Published trigger connected to AI Generate Text, then to Post to All Social.

Option 2: Review before publishing

1. Trigger: Post Published
2. Action 1: AI Generate Text — generate the social copy, store as social_copy
3. Action 2: Store Social Content — save to post meta using {{post_id}}
4. Action 3: Send Email to the editor containing the draft social copy for review
5. Publish manually once reviewed

Option 3: Scheduled daily social posts

1. Trigger: Schedule (daily, 9:00 AM)
2. Action: AI Generate Text — generate fresh copy for the day
3. Action: Post to All Social using the AI output

Real-world automation examples #

Auto-publish a new post across all social platforms Trigger:

Post Published Action 1: AI Generate Text with a prompt to write optimised copy for each platform Action 2: Post to All Social with the AI output as the message

New WooCommerce product announcement Trigger:

WooCommerce Product Back in Stock (or a custom webhook trigger) Action: Post to All Social announcing the product with {{product_name}} in the message

Generate and store social copy for manual review

Trigger: Post Published Action 1: AI Generate Text producing three platform-specific versions Action 2: Store Social Content saving each version as post meta Action 3: Send Email to admin with the generated copy for approval

Pre-built templates #

Install these from Krom Automation > Templates:

Template	What it does
publish-to-social-on-post	Publishes to all social platforms when a WordPress post is published
ai-content-create-and-share	AI generates social copy and publishes it to all platforms
ai-blog-post-new-product	AI generates a blog post when a new WooCommerce product is published

Troubleshooting on social media integration #

Social posting actions are failing

Check the execution log for the specific error message. The most common cause is an expired or invalid access token. Go to Krom Automation > Settings > Social Media, generate a fresh token from the platform’s developer portal, update the field, and save.

Twitter/X posts are being rejected

Confirm your Twitter Developer app has Read and Write permissions enabled. Tokens generated under a read-only app cannot post. If you changed permissions after generating your token, you need to generate a new token- existing tokens don’t inherit updated permissions.

Facebook posts aren’t appearing on the page

Confirm the Page Access Token is scoped to the specific Facebook Page you want to post to. A user access token is not the same as a page access token. Also verify the token includes the pages_manage_posts permission scope.

The Post to All Social action partially fails (some platforms post, others don’t)

Each platform posts independently. If one platform’s credentials are invalid or expired, that platform will fail while others succeed. Check the step detail in the execution log to see which platform returned an error.