Make employee review signals part of your routine
Let Notis gather Akta employee reviews for selected businesses in your Notion research as part of a monthly review.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Akta Employee Reviews
Fetch a company's employee review signals and reviews.
Why this helps
Workplace perspectives are easy to overlook when company research is spread across many sources.
- Bring workplace perspectives into a regular review.
- Avoid remembering to search each company separately.
- Keep relevant employee signals alongside your research routine.
Setup
Build it in a few focused steps.
- 1Connect Notion and Akta to Notis once through the portal.
- 2Create an automation with one instruction for which tracked companies should receive an employee review check.
- 3Select a recurring monthly schedule.
- 4Choose a channel for run reports and test with one real company.
Questions about this workflow
Does Akta guarantee reviews for every company?
No. Akta fetches available employee review signals and reviews for a company.
Can this run less often?
Yes. Choose the recurring cadence that matches how often you review company research.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Akta. A trigger fires from one place; an action lands in another.
Notion triggers
Akta actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Akta Industry Search
Resolve a free-text industry topic into industry codes.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Akta Company Enrichment
Enrich a company with firmographics, business model, headcount, website traffic, funding, financials, founders, acquisitions, and investment data.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Akta News
Fetch enriched news articles for a company, open-ended topic, or industry — funding rounds, M&A, leadership changes, and more.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Akta Company Search
Locate a company by name or website to get its uuid/website.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Akta Employee Reviews
Fetch a company's employee review signals and reviews.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Akta Product Reviews
Fetch a company's product catalog and per-product reviews.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion and Akta, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Akta.