Custom Fields
Save account-specific details once, reuse them in every post
A RecurPost custom field stores an account-specific detail once, then drops that detail into your posts for you. Agencies and freelancers use custom fields to stop retyping the same address, phone number, or booking link on every near-identical post they write for a different client. You save the value one time per account, and RecurPost fills it in when the post publishes. Custom fields live inside the RecurPost composer, next to the other tools you use to build a post.
No credit card required.
What a custom field is in RecurPost
A RecurPost custom field is a saved key-value pair that holds account-specific information. You create the pair once and reuse it on as many posts as you want. Most schedulers call this “personalization” and leave it vague — RecurPost makes it concrete.
A named key
The key is a label like StoreAddress or BookingURL.
One saved value
The value is the real text, such as a clinic street address or its appointment link.
Kept in a central list
One named field with one saved value, not free text you paste again on every post.
Fits static details
An address, a phone number, a booking URL, an email signature, or a business name.
Take a freelancer who runs social for 12 dental clinics. Every clinic gets the same weekly checkup reminder — only the address and the booking link change. The freelancer writes the reminder once, and each clinic page fills in its own saved address and link.
A custom field does not fit a per-platform wording change or an @mention. RecurPost handles those two jobs with different tools, covered further down.
How it works
How to create a custom field in RecurPost
You create a RecurPost custom field in the Plug-ins area. Add the field name and its value, then save.
Click your name
Open the menu at the bottom-left of your RecurPost dashboard.
Open Plug-ins
Select Plug-ins from the menu.
Find Custom Fields
Click Manage on the Custom Fields plug-in.
Add name and value
Enter the field name and the real text it should hold.
Save
The field stays available until you change it.
RecurPost also lets you add a field inline. While you write a one-off post or add content to a library, you can open custom fields and create a new one without leaving the composer.
An agency usually sets these up during client onboarding: for each connected account, add one BookingURL field and one StoreAddress field. From then on, every post for that account can pull those values. A detail you will use in a single post does not need a custom field.
In the composer
Insert a custom field while composing or building a library
You insert a RecurPost custom field at two points. In both places you pick the field from your saved list, and RecurPost drops a placeholder token into the post text.
From the calendar
Insert a field while you schedule a one-off post.
From a content library
Write one library post, insert the field, and queue it to many accounts at once.
RecurPost makes custom fields scale through the library route. Each account resolves the token to its own saved value, so one library post serves every account it publishes to.
RecurPost reads custom fields from the values you saved in your field list — they are not a live merge from an outside CRM or spreadsheet. The value that publishes is the value you stored in RecurPost.
Pick a saved field while you compose — RecurPost drops a placeholder token into the post text.
At publish time
What custom fields look like at publish time
A RecurPost custom field shows as a placeholder while you write, then renders its saved value on the published post.
A token while you write
The field appears in the editor as a short placeholder token.
The value when it goes live
The saved value may not show in the editor preview; it appears once the post publishes.
Two character counts
RecurPost counts the token, while each social platform counts the resolved value.
Keep values short
Check the resolved length before you schedule to tight-limit platforms.
A short token can hide a long value. Picture a store address saved as a custom field: in the editor the token looks short and the post fits. Once it resolves on X, the full address pushes the post past the character limit and the post can fail.
Built for scale
Using custom fields across many client and location accounts
RecurPost scopes each custom field to a connected account. That scoping is the whole point: one post template can resolve to the right address, phone, and link for every account it publishes to.
A franchise marketer feels this most. Picture one promo post pushed to 28 location accounts. Each location holds its own address field and its own phone field. The marketer writes the promo once, and all 28 posts go out with the correct local details.
RecurPost keeps your message consistent while each account keeps its own data. The brand wording stays identical across locations; the address, phone, and link stay local. RecurPost prices the Agency plan around 20 social accounts on flat per-profile pricing with no per-user seat charge, so custom fields scale across every client account you connect.
A solo operator who runs a single account gains little here. Custom fields pay off when you have many accounts that share content but differ on a few saved details.
Pick the right tool
When to use a custom field, and when to use something else
Use a RecurPost custom field for static, repeated, account-specific text. RecurPost gives you a different tool when the job is something else.
| The job | RecurPost tool | What RecurPost does |
|---|---|---|
| Insert a repeated account detail (address, phone, link) | Custom field | RecurPost saves the value once per account and fills it in at publish. |
| Change wording or format for each platform | Tailored Posts | RecurPost builds a separate variant for each network from one composer. |
| Mention another account with an @tag | Tag Users | RecurPost adds platform mentions and tags to the post. |
| Write new caption or post copy | AI Content Generator | RecurPost generates the text for you in the composer. |
RecurPost makes the call with a simple test. If a client needs a different phone number on every post, RecurPost treats that as a custom field. If a post needs a shorter caption on X than on LinkedIn, RecurPost treats that as a tailored post, not a custom field.
Custom fields and bulk upload: RecurPost pairs custom fields with bulk scheduling. When you import many posts at once through an Excel or CSV upload, your saved fields still resolve per account, so a large import keeps each account’s local details intact.
Try RecurPost free
RecurPost lets you save account-specific custom fields once and reuse them across every connected client account. The Agency plan includes around 20 social accounts on flat per-profile pricing with no per-user seat charge, so your custom fields scale as you add clients.
No credit card required.
— FREQUENTLY ASKED —
Frequently asked questions
What is a custom field in RecurPost?
A RecurPost custom field is a saved account-specific detail that fills into your posts automatically. It holds a value such as an address, a phone number, or a booking link under a named field. You save it once and reuse it across many posts.
Where do I create custom fields?
You create custom fields under Plug-ins. Click your name at the bottom-left, open Plug-ins, select Custom Fields, and click Manage. RecurPost also lets you add a field inline while you compose a post or build a library.
Why do my custom field values not show in the editor?
Your custom field value renders on the published post, not always in the RecurPost editor preview. RecurPost shows a placeholder while you write. The saved value appears once the post publishes on your social account.
Can custom fields be different for each social account?
RecurPost defines custom fields per connected account, so each account holds its own values. One post template resolves to the correct address, phone, and link for each account it publishes to. That scoping is what lets one template serve many clients or locations.
Do custom fields affect character limits?
Custom fields can affect character limits, because RecurPost counts the field token while each platform counts the resolved value. A short token can resolve to a long value and push a post past a platform limit. Check the resolved length before you schedule to tight-limit platforms like X.
