Connect Adtraction to Byteforms

When something happens in Adtraction, Notis takes the next step in Byteforms. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Adtraction to Byteforms

View example

Create an Affiliate Partner Intake Form

Create a Byteforms form to collect partner details when an Adtraction partner request arrives through a Notis webhook.

View example

Review Affiliate Lead Form Responses Weekly

On a schedule, retrieve responses from a Byteforms affiliate lead form so Notis can summarize pending partner leads for your run report.

View example

List Affiliate Forms for a Webhook Review

When a Notis webhook starts the workflow, list your Byteforms forms so Notis can report which forms are available for affiliate operations.

View example

Check Partner Form Details on a Schedule

Retrieve a specified Byteforms form on a schedule and report its available details for a recurring affiliate workflow check.

View example

Triage Affiliate Submissions from a Webhook

Fetch responses for a specified Byteforms form when a Notis webhook starts, then summarize submissions that appear to need follow-up.

View example

Create a Campaign Feedback Form

Create a Byteforms form on a schedule for collecting structured affiliate campaign feedback from partners.

View example

Look Up a Partner Form from a Request

Retrieve a Byteforms form by ID when a Notis webhook starts, then report its details alongside the incoming request context.

View example

Refresh Your Affiliate Form Catalog

On a recurring schedule, list Byteforms forms and produce a concise catalog to help you locate forms used in affiliate operations.

View example

Review Partner Feedback Responses on Demand

Fetch responses to a Byteforms partner feedback form when a Notis webhook starts and summarize themes for review.

Supported Triggers and Actions

Notis builds workflows that link Adtraction to Byteforms. A trigger fires from one place; an action lands in another.

Adtraction triggers

Byteforms actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create form

Creates a new form.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete Form

Permanently deletes a form.

ActionInstant

Get all forms

Lists all forms created by the authenticated user.

ActionInstant

Get Form By ID

Retrieves details about a specific form.

ActionInstant

Get Form Responses

Retrieves responses submitted to a form.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.