UncrownedGuard

I would love to see Invision Pages receive expanded Zapier support, especially for workflows involving automated article, database, and content publishing. Right now, Zapier already works well for creating Pages records, but there are a few missing pieces that make automation feel incomplete. Add Support for Meta Keywords and Meta DescriptionThe biggest missing fields are Meta Keywords and Meta Description. These are ideal candidates for automation because they are structured, predictable, and often generated alongside article titles, excerpts, tags, and body content. It feels like an odd omission since Zapier can already populate many other record fields, but not these SEO fields. Being able to fill these directly through Zapier would make automated Pages publishing much more complete and reduce the need to manually revisit each record after creation. Add a “Find Record” Action for Pages DatabasesAnother major improvement would be a Find Record action for Invision Pages. Zapier currently supports finding things like topics, blogs, clubs, and members, but there does not appear to be an equivalent way to find a Pages database record. This would be extremely useful for workflows where a record needs to be referenced, updated, checked, or used as supporting data without that record itself being the original trigger. For example, a Zap could find an existing Pages record, pull its title, URL, image, custom fields, or other details, and then use that information in a newsletter, social media post, internal workflow, or another automated action. This allows users to use triggers like scheduled runs, RSS feeds, etc., and gain the full record details. Support Upload Fields Through ZapierI know this may be more technical, but it would also be great if upload fields could eventually be supported through Zapier. The most obvious use case would be featured images or other image/file upload fields attached to Pages records. Even if this started with basic support, such as accepting a file URL from a previous Zapier step, it would make Pages automation significantly more powerful. Why This MattersInvision Pages is one of the most flexible parts of the platform, and Zapier support makes it possible to build strong publishing and community workflows without custom development. Adding support for Meta Keywords, Meta Description, Find Record, and eventually upload fields would make Pages much more practical for automated content pipelines while keeping everything inside the Invision ecosystem. These additions would be especially valuable for communities using Pages as a news system, article hub, database, resource directory, or structured publishing platform.

I love this feature, and I’m really excited to start putting it into motion. The whole workflow system feels like it’s going to make Pages databases so much smoother to manage as a team. That said, the permissions side of it is a bit confusing. I still can’t figure out how to get a team to actually show up as an assignment option, even though assigning to a member or team is listed as one of the available workflow actions, but some admins are not shown either. I’ve gone through the usual permission areas, but something still isn’t clicking. I’m sure it’s just one setting I’m overlooking, but if anyone has already sorted this part out, I’d definitely appreciate a pointer.

When adding events in IC5, if you add them via the "Add Similar Event" feature, it removes the cover image upload field when adding the new event, and also if you try to edit the event after posting it. You can still add and adjust a cover image via the Cover Image drop-down on the display page after it is posted. This affects both my cloud communities and self-hosted communities running the latest IC5. Adding an event normally appears to be working as intended, and has the cover image upload field when first posting and also when editing.

This one is actually on YouTube, not Invision. The playlist embed itself is working correctly in IC5; the problem is that YouTube has been stripping features out of their embedded player over time. The old corner menu that lets you open the full playlist is gone. YouTube removed that from their embed UI, so Invision can’t bring it back. At this point, the only playlist controls YouTube still exposes in embeds are the next/previous arrows, and those only appear once the video is paused or finished. So the behavior you’re seeing isn’t a bug in Invision or something missing in IC5; it’s just YouTube continuing to limit what their embeds can do. When you embed a playlist, it is now supposed to look like a single video.

You can also make Blocks for ads now, and this is how I handle most of my ads. The Block positions are more than enough to meet my needs. I also use the block visibility features to handle things like mobile vs desktop ads and their permissions to handle who sees what ads.

I wish the “Free Trial” button would switch to “Client Area” once you’re logged in or once you own a product. It’s a small detail, but it feels unintuitive that the only real confirmation you’re logged in is inside the community itself. Having that top‑level indicator would make the whole experience feel more cohesive. I’m also hoping some of the new homepage blocks and layout elements eventually make their way into Pages. One of the biggest strengths of Invision is that it’s an all‑in‑one platform capable of powering the entire website, but right now, a lot of what’s shown on the main site can’t be recreated without heavy customization. This is a minor thing and more of just constructive criticism. Plus, more Pages features are always a perk. Overall, the redesign looks great. I’d just love to see the client area get a visual refresh to match the new style, and I agree that the forum could be a bit more prominent. The community side of Invision Community is a huge part of what sets it apart from other platforms; it wouldn’t hurt to showcase that strength a little more.

This is the wet dream of my use for the Pages app! Looking forward to it!

Okay, like everything, I have overcomplicated it. I would like to use this in a Yes/No field. I tried this code, but it does not seem to pull the information and just makes a blank space. This is also he field URL: membersettings&controller=profiles&tab=profilefields&subnode=1&do=form&id=3 It does pull the <hr> line, so that is something. {{if $formValue == "1"}} {{if $record->author()->contentProfileFields()['core_pfieldgroups_1']['core_pfield_3']}} <hr> <div class="author-info"> <p> {$record->author()->contentProfileFields()['core_pfieldgroups_1']['core_pfield_3']|raw} </p> </div> {{endif}} {{endif}}

My site does a lot of news, and at the bottom of the news, I have a custom field set up to pull in a bio for the author. Right now, that is simply a select box that you can select the author, and it pulls a simple preformatted HTML-based bio over (essentially, it is just using the standard select box custom field as intended. This works well, but it does leave room for error where one author can select the wrong author bio, and only admins can edit the bio for others. What I would LOVE to do is have a custom profile field, where the user can create, edit, and format their author bio, and when they post news, it pulls that field into the news record. I feel like this is possible as the custom fields have all sorts of relations and features, but I have never found a real guide on how to use these. Any help is appreciated. In summary, I want to create a custom profile field called "Author Bio" that uses the standard editor to create the content. Then pull that content into a custom page's record field. Either via something like a Yes/No field that will display or not display the author bio, or simply added to always appear.

This is what Google led me to as well, but I can confidently say that the URL (or title in this case) has zero impact on the error being presented by Zapier. A page database record. Yes, the real count including HTML.

Does the Zapier process have a max input for the content field? I generally receive a 414 error and without much information, it appears that anything above 5000 characters causes this. Sadly the only error log is "the app returned "414"." in Zapier and there is no log in Invision that I know of, so it is a guess here. But limiting the content input to under 5000 characters appears to work. This is the default content field for a database in Pages by the way.

So the only thing I noticed (and idk if this is a PWA limitation or not as I dont use them much), but if you accidentally deny the push permissions or if you let it timeout and it auto denies them, then you get stuck with a message that the permissions were denied and there is no way to request them again. This is kind of a burden in a PWA as you don't have great access to browser settings to fix this without leaving the PWA app and going into the browser directly and all that.

If I could, I'd gladly buy you all a round of drinks for this one! Thank you!

Is this part of all cloud communities or is this part of the AI image moderation listed for Business level and up?

Is it possible to bring an existing Cloud community to IC5 at this point?