Connect Spotify to Bigpicture io

When something happens in Spotify, Notis takes the next step in Bigpicture io. 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 Spotify to Bigpicture io

View example

Find company domains from playlist changes

When a Spotify playlist changes, identify company names in the update and find likely domains for research.

View example

Look up company profiles from playlist updates

Use a changed Spotify playlist to identify a company and retrieve its profile by confirmed domain.

View example

Enrich playlist-linked companies from an IP

When a playlist change includes an IP clue, use Bigpicture io to identify the related company.

View example

Discover company domains from new playlists

When a Spotify playlist is created, identify any company names in its context and find likely domains.

View example

Profile a company named in a new playlist

Use a confirmed domain from a newly created Spotify playlist to retrieve detailed company data.

View example

Research a company from a playlist IP clue

When a playlist is created or deleted with an IP clue, look up the related company in Bigpicture io.

View example

Find company domains from new device context

When Spotify reports a new device, identify company names in the context and search for likely domains.

View example

Look up a company profile from a new device

Use a confirmed company domain from a Spotify new device event to retrieve detailed company data.

View example

Identify companies from device event IPs

When a new Spotify device event includes an IP, use Bigpicture io to identify the related company.

Supported Triggers and Actions

Notis builds workflows that link Spotify to Bigpicture io. A trigger fires from one place; an action lands in another.

Spotify triggers

Bigpicture io actions

Recurring trigger

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

TriggerScheduled

Company Find

Tool to lookup company data by domain name. use when you need detailed company profile by providing a website domain. use after confirming domain correctness.

ActionInstant

Webhook trigger

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

TriggerInstant

IP to Company Lookup

Tool to lookup company by ip address. use after obtaining an ip to get detailed company info.

ActionInstant

New Device Added

Triggers when a new device is added.

TriggerPolling

Name to Domain Search

Tool to find company domain(s) by company name. use when you have a company name and need up to 3 likely domains.

ActionInstant

Spotify Playlist Item Change

Triggers when songs are added to or removed from a Spotify playlist.

TriggerPolling

New Playlist Created or Deleted

Triggers when a new playlist is created or deleted.

TriggerPolling

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.