Connect Slack to Ip2proxy
When something happens in Slack, Notis takes the next step in Ip2proxy. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Slack to Ip2proxy
Check login IPs shared in Slack
When someone posts an unfamiliar login IP in a Slack channel, have Notis check whether it is associated with a proxy, VPN, or Tor.
Review signup IPs shared in Slack
Check an IP posted in a signup-review channel so the team can factor proxy, VPN, or Tor status into its signup review.
Check IPs from support access reports
When a support team shares a customer access IP in Slack, check it for proxy, VPN, or Tor status to help frame the investigation.
Check vendor connection IPs
Check a vendor's IP when it is shared in Slack so the team can see whether Ip2proxy classifies it as a proxy, VPN, or Tor.
Check source IPs in webhook alerts
When an alert message includes a source IP, check its proxy, VPN, or Tor status to give incident responders another clue.
Check IPs sent to you in Slack
When someone sends you an IP in a Slack DM, check it with Ip2proxy so you can get proxy, VPN, or Tor context without opening another tool.
Review deployment IPs posted in Slack
Check an IP shared in a deployment discussion when the team wants proxy, VPN, or Tor context before reviewing access or traffic.
Check IPs raised in fraud reviews
Check IPs mentioned in Slack fraud review discussions for proxy, VPN, or Tor status and return the result for human review.
Check account recovery IPs
When an account recovery IP is shared in Slack, ask Ip2proxy to check proxy, VPN, or Tor status for the team's review.
Supported Triggers and Actions
Notis builds workflows that link Slack to Ip2proxy. A trigger fires from one place; an action lands in another.
Slack triggers
Ip2proxy actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Proxy Status of an IP
Tool to check if an IP address is a proxy. Use after obtaining an IP to detect proxy, VPN, or Tor status.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
New Channel Created Trigger
Triggered when a new channel is created in Slack.
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Slack and Ip2proxy
Connect any two apps with Notis in the middle.
Slack and Ip2proxy, 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 Ip2proxy.