Connect Acculynx to Backendless

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

View example

Alert the team when an AccuLynx lead needs follow-up

Send a Backendless notification when an AccuLynx lead arrives, including the lead details and a suggested next step.

View example

Share a concise brief for AccuLynx project changes

Publish a short Backendless update when a webhook reports an AccuLynx project change, with what changed and what may need attention.

View example

Notify the team about AccuLynx task assignments

Publish an assignment notice to Backendless when an incoming webhook includes an AccuLynx task assignment and its available context.

View example

Organize incoming job documents in Backendless

Create a Backendless directory for a job when a webhook supplies its identifying details, giving documents a consistent place to land.

View example

Copy selected AccuLynx job files into Backendless storage

Copy a job file within Backendless storage after a webhook request provides verified source and destination paths.

View example

Review open AccuLynx leads on a schedule

On a recurring schedule, retrieve matching lead records from a confirmed Backendless table and produce a concise review from the returned data.

View example

Check Backendless project records for missing details

Run a scheduled query of project records and summarize missing or inconsistent details that can be assessed from the returned fields.

View example

Count job files in Backendless storage

On a schedule, count files in a specified Backendless directory so the run report shows whether the stored job materials have changed.

View example

Look up a Backendless user from an AccuLynx request

Retrieve user information by Backendless object ID supplied in a webhook request and summarize only the useful returned details.

Supported Triggers and Actions

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

Acculynx 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

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.