Skip to content

Integration · Data and databases

ApptiveGrid in Skyller.

Connect ApptiveGrid to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.

Actions and events

ApptiveGrid

ApptiveGrid is a collaborative no-code database and app platform for managing spaces, grids, forms, and structured records.

Actions
7
Events
0
Composio catalog
API key
Global — no specific country
re-read from the vendor every 24 hours
apptivegrid.de

7 ACTIONS

published by the vendor; the company enables only the necessary ones

0 EVENTS

triggers the system can send, when the vendor offers them

API KEY

each person signs in with their own credential, encrypted

APPROVAL BY RISK

sensitive actions show a card before running

Live proof

One request, one query in ApptiveGrid and one approval.

The scene shows the path of a request; the exact actions depend on the functions your company enables in ApptiveGrid.

  1. Input

    A team member asks, in the conversation, for something that today requires opening ApptiveGrid — inside their area's space, with their login.

  2. What Skyller does

    1. 01Picks, among the enabled functions, a query action and looks the information up in ApptiveGrid with the person's own credential.
    2. 02If the request requires writing something in ApptiveGrid, shows the card with what it is about to do and waits for Approve.
    3. 03Returns the result in the conversation and records who asked, which action was used and when.
  3. Result

    ApptiveGrid stops being an open tab and starts answering inside the conversation — through the functions your company enabled.

What this scene does not promise

  • The available actions are the ones the vendor publishes for ApptiveGrid; in your company only the functions turned on by the administrator are available.
  • If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
  • Being in this catalog does not mean being installed, with a valid login, working in your company.

Where this helps your work

ApptiveGrid inside the conversation where the work happens.

Three common situations for people who use ApptiveGrid every day. What Skyller does in each one depends on the functions your company turns on.

Needing the information now

“What is recorded in ApptiveGrid about this?”

The person asks in the conversation and Skyller queries ApptiveGrid with their login, through the enabled read functions, and answers with what it found.

System data in the answer

Recording the result

“Log this in ApptiveGrid.”

Creating or changing a record is a write action: Skyller shows the card with what it is about to do and waits for Approve before touching ApptiveGrid.

Action with approval

Administering

“Enable only what this team needs.”

The administrator connects ApptiveGrid once, turns on the necessary functions, restricts them to groups and follows the record of every call.

Function by function, with a record

Actions and events

What the vendor offers in ApptiveGrid.

Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.

  • Create Record

    APPTIVEGRID_CREATE_RECORD

    Create one record in a grid from a provider-native object keyed by that grid's field IDs or field keys; inspect the grid first to construct valid values.

  • Get Current User

    APPTIVEGRID_GET_CURRENT_USER

    Return the connected ApptiveGrid user's ID, plan, seat availability, and resource links; use it to identify the user before listing spaces.

  • Get Grid

    APPTIVEGRID_GET_GRID

    Return a grid's metadata and dynamic field definitions; use it before listing, reading, or creating records.

  • Get Record

    APPTIVEGRID_GET_RECORD

    Return one record from a grid by record ID, optionally rendered with a provider layout.

  • Get Space

    APPTIVEGRID_GET_SPACE

    Return a space and its grid summaries or grid links; use it to discover grid IDs before reading records.

  • List Records

    APPTIVEGRID_LIST_RECORDS

    Return one 1-based page of records from a grid, optionally using the provider's layout, filter, and sorting definitions.

  • List Spaces

    APPTIVEGRID_LIST_SPACES

    Return one 1-based page of spaces available to a user, including IDs needed to inspect a space.

Before you start

What your company needs to use ApptiveGrid.

Login
Each person enters their own ApptiveGrid API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs
An administrator connects ApptiveGrid for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions
7 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan
Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.

Questions from the people who decide

Common doubts before connecting ApptiveGrid.

Next step

Connect ApptiveGrid and try it with your team.

Try it free with your team or book a demo: together we pick the ApptiveGrid functions to enable and show the first approved action, with fictitious data.