When data received from Integrately, update post meta in WordPress

When an Integrately automation sends data to FlowMattic, this workflow writes it to a custom field on a WordPress post, so values from your other apps end up stored with the right post.

Integrately

WordPress

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 2.8k sites Free to import

The When data received from Integrately, update post meta in WordPress workflow on the FlowMattic canvas, with 2 steps across Integrately, WordPress — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

You may already run automations in Integrately that hold data your WordPress posts should carry. Post meta is where WordPress keeps a post's extra data: custom fields, prices, ratings, external IDs. This workflow lets an Integrately automation pass values in, and FlowMattic saves them on the post you name.

The Integrately trigger receives the data your Integrately automation sends to FlowMattic. Whatever that payload contains becomes available to map. The WordPress step then runs Update Post Meta on your site, using the values you map into it.

The post to update has to be identified by the incoming data, so build your Integrately automation to send the WordPress post ID along with the values you want stored. Run a test with a known post after import and check the custom field on that post. Task History logs every run, including the payload Integrately sent.

Store an external record ID on a post

An Integrately automation creates a record in another app for each article and sends the new record ID back, so it is saved as meta on the matching post.

Refresh a listing's price from another tool

Your prices live in an app Integrately connects to. When a price changes there, Integrately sends the post ID and new price, and the post's meta field is updated.

Save review scores against product posts

A review platform's rating reaches Integrately, which passes it with the post ID so the score is kept on the post for your theme to display.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Integrately Receive Data
Runs when your Integrately automation sends data to this workflow. Every value in the payload is passed on for mapping. Include the WordPress post ID in what Integrately sends.
Step 2Action
WordPress Update Post Meta
Updates post meta on your WordPress site with the values you map from the Integrately data. Map the incoming post ID so the right post is changed, then test it on a post you know.

What you need

FlowMatticCore
Integrately AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Add a Filter after the trigger that continues only when the post ID in the payload is not empty, so runs without a target post stop before the WordPress step.
Send one test payload from Integrately after import. FlowMattic captures its fields, and you can map the post ID and value into the WordPress step.
If one payload should update several meta keys, add another Update Post Meta step for each extra key.

Questions about this workflow

How does the workflow know which WordPress post to update from the Integrately data?

From the data Integrately sends. Include the post ID in your Integrately automation's payload, then map it in the Update Post Meta step.

Does this need FlowMattic and the posts on the same WordPress site?

Yes. The Update Post Meta step changes posts on the site where FlowMattic is installed.

Which meta key does the Integrately data update?

The key you set up in the WordPress step after import. Send a test payload and check the custom fields on that post to confirm the value landed under the key you expect.

What if the post ID Integrately sends is wrong?

The WordPress step works with whatever ID it receives, so the wrong post could be changed or nothing updated. Test with a known post and check Task History for the result.