Nota’s assistive AI tools help publishers create headlines, summaries, SEO keywords and more.

heynota

<p>Nota is a SaaS company building AI-enabled tools to streamline content creation and distribution. Their assistive AI tools help publishers, marketers and content creators generate headlines, summaries, SEO keywords and more.</p>
<p>Nota is taking the pain points out of the content creation process so you can focus on what really matters: your story.</p>
<h3>Dissect Content with Speed.</h3>
<p>The Nota plugin is a time-saving tool for editorial, marketing and content teams focused on optimizations—generating headlines, summaries, top quotes, key points, SEO keywords and categories. The plugin utilizes large language models to generate AI responses, returning robust copy results.</p>
<p>Nota runs text through uber-powerful AI and ML tools to break down all that content into workable outputs. No prompts or queries, no AI learning curves, just quick-and-easy text applications. Analyze a post and tailor the outputs for more, less or just different results with the push of a button. If you’re looking for a human touch, you can edit the outputs directly to your liking.</p>
<h3>Custom Fields</h3>
<p>When users choose to use outputs provided by Nota, the plugin will update the appropriate fields on the post. For example, selecting a “Headline” will update the post title.</p>
<p>This behaviour can be changed if custom fields are required, by using the <a href="https://developer.wordpress.org/block-editor/reference-guides/packages/packages-hooks/" rel="nofollow ugc">@wordpress/hooks</a> functionality.</p>
<p>Each field has a corresponding getter and setter function. The filter names follow the pattern: <code>nota.postData.<fieldName>.get</code> and <code>nota.postData.<fieldName>.set</code>. The following filters are available:</p>
<ul>
<li><code>nota.postData.title.get</code></li>
<li><code>nota.postData.title.set</code></li>
<li><code>nota.postData.excerpt.get</code></li>
<li><code>nota.postData.excerpt.set</code></li>
<li><code>nota.postData.slug.get</code></li>
<li><code>nota.postData.slug.set</code></li>
<li><code>nota.postData.metaTitle.get</code></li>
<li><code>nota.postData.metaTitle.set</code></li>
<li><code>nota.postData.metaDescription.get</code></li>
<li><code>nota.postData.metaDescription.set</code></li>
</ul>
<p>For example, to use a custom field for the title, you would implement the following:</p>
<pre><code>const customTitleMetaKey = 'my-custom-meta-key'

const getTitle = () => {
  return wp.data.select('core/editor').getEditedPostAttribute('meta')[customTitleMetaKey]
}
wp.hooks.addFilter('nota.postData.title.get', 'custom/namespace', () => getTitle )

const setTitle = (nextValue) => {
  wp.data.dispatch('core/editor').editPost({ meta: { [customTitleMetaKey]: nextValue } })
}
wp.hooks.addFilter('nota.postData.title.set', 'custom/namespace', () => setTitle )
</code></pre>
<h3>Access Control</h3>
<p>Nota supports restricting plugin access to specific users via a WordPress filter.</p>
<p>For advanced use cases, you can use the <code>nota_tools_user_allowed</code> filter to implement custom access logic:</p>
<pre><code><?php
/**
 * Filter: nota_tools_user_allowed
 * 
 * @param bool    $allowed Whether the user is currently allowed (default: user can edit_posts).
 * @param WP_User $user    The current user object.
 * @param array   $context Context about where the check is being made.
 *                         Keys:
 *                         - 'area': The feature area being accessed.
 *                           Values: 'post_tools', 'draft', 'dashboard', 'news'.
 *                         - 'post_id': The post ID if applicable.
 */
add_filter( 'nota_tools_user_allowed', 'my_custom_nota_access', 10, 3 );
</code></pre>
<p><strong>Example: Allow access based on a custom user profile field:</strong></p>
<pre><code><?php
add_filter( 'nota_tools_user_allowed', function( $allowed, $user, $context ) {
    // Only allow users with 'nota_access' meta set to 'yes'
    $nota_access = get_user_meta( $user->ID, 'nota_access', true );
    return $nota_access === 'yes';
}, 10, 3 );
</code></pre>
<p><strong>Example: Allow access based on email domain (e.g., for pilot rollouts):</strong></p>
<pre><code><?php
add_filter( 'nota_tools_user_allowed', function( $allowed, $user, $context ) {
    // Only allow users with @californiapost.com email addresses
    $email = $user->user_email;
    return substr( $email, -strlen( '@californiapost.com' ) ) === '@californiapost.com';
}, 10, 3 );
</code></pre>
<p><strong>Example: Combine default access with additional custom logic:</strong></p>
<pre><code><?php
add_filter( 'nota_tools_user_allowed', function( $allowed, $user, $context ) {
    // If already allowed by default, also require specific role
    if ( $allowed ) {
        return in_array( 'editor', $user->roles, true );
    }
    return false;
}, 10, 3 );
</code></pre>
<h3>Developer Filters</h3>
<p>Nota provides several filters for customization:</p>
<h4>nota_tools_user_allowed</h4>
<p>Controls whether a user can access Nota tools. See “Access Control” section above.</p>
<h4>nota_tools_supported_post_types</h4>
<p>Customize which post types display Nota tools:</p>
<pre><code><?php
add_filter( 'nota_tools_supported_post_types', function( $post_types ) {
    // Add custom 'article' post type
    $post_types[] = 'article';
    return $post_types;
} );
</code></pre>
<h4>nota_tools_supported_components</h4>
<p>Enable or disable specific Nota tool components:</p>
<pre><code><?php
add_filter( 'nota_tools_supported_components', function( $components ) {
    // Disable hashtags component
    $components['hashtags'] = false;
    return $components;
} );
</code></pre>


Alternatives to Nota

Top alternatives