Skip to content
Notis

Coordinate investor introductions in a shared channel

Turn an introduction request into a concise team message that makes the context and next step easy to find.

Trigger

Webhook received

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

Action

Publish Message

Publish a message to a channel for its subscribers.

Why this helps

Introduction requests can disappear in individual workflows when the team needs to coordinate a response.

  • Make introduction requests visible to collaborators.
  • Summarize the supplied context in a consistent format.
  • Help the team agree on the next step sooner.

Setup

Build it in a few focused steps.

  • 1Connect Affinity and Backendless once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it for investor introductions.
  • 3Tell Notis to summarize the introduction context included in each request and publish the next step to a specified Backendless channel.
  • 4Choose the webhook trigger and select where run reports should go.
  • 5Test with one real introduction request and verify the message is clear and accurate.

Questions about this workflow

Does Notis detect introductions in Affinity automatically?

No. Affinity has no listed trigger events. Start the workflow with an HTTP request that includes the introduction details.

Can Notis decide whether to make an introduction?

The prompt can help summarize and route the supplied information, but any decision criteria must be stated by you and supported by the supplied context.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Affinity triggers

Backendless actions

Recurring trigger

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

TriggerScheduled

Copy File

Copy a file or directory in file storage.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Directory

Create a directory in file storage.

ActionInstant

Create Backendless Hive

Create a Hive.

ActionInstant

Create Backendless Timer

Create a timer for scheduled server-side tasks.

ActionInstant

Delete Directory

Delete a directory from file storage.

ActionInstant

Delete File

Permanently delete a file from storage; this cannot be undone.

ActionInstant

Delete Backendless Timer

Immediately and permanently delete a timer, stopping scheduled runs; this cannot be undone.

ActionInstant

Directory Listing

List files and directories in storage.

ActionInstant

Connect any two apps with Notis in the middle.

Affinity and Backendless, 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 Backendless.