Accept Completion with Sapling.ai API on New Transfer Status from OpenSRS API

Pipedream makes it easy to connect APIs for Sapling.ai , OpenSRS and 2,800+ other apps remarkably fast.

Trigger workflow on

New Transfer Status from the OpenSRS API

Next, do this

Accept Completion with the Sapling.ai API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a OpenSRS trigger and Sapling.ai action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Transfer Status trigger
1. Connect your OpenSRS account
2. Configure Polling Schedule
Configure the Accept Completion action
1. Connect your Sapling.ai account
2. Configure Completion ID
3. Optional- Configure Session ID
4. Configure Query
5. Configure Completion
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Transfer Status on OpenSRS

Description:Emit new event when the status of a domain transfer changes. [See the documentation](https://domains.opensrs.guide/docs/status_change-transfer).

Version:0.0.1

Key:opensrs-new-transfer-status

View on GitHub

Trigger Code#

import common from "../common/polling.mjs";
import events from "../common/events.mjs";
import constants from "../../common/constants.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  ...common,
  key: "opensrs-new-transfer-status",
  name: "New Transfer Status",
  description: "Emit new event when the status of a domain transfer changes. [See the documentation](https://domains.opensrs.guide/docs/status_change-transfer).",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  methods: {
    ...common.methods,
    isResourceRelevant(resource) {
      return resource.object === constants.OBJECT_TYPE.TRANSFER
        && resource.event === events.STATUS_CHANGE;
    },
    generateMeta(resource) {
      return {
        id: resource.event_id,
        summary: `New Transfer Status: ${resource.objectData.domain_name}`,
        ts: Date.parse(resource.event_date),
      };
    },
  },
  sampleEmit,
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
OpenSRS	`app`	`app`	This component uses the OpenSRS app.
Polling Schedule	`timer`	`$.interface.timer`	How often to poll the API

Trigger Authentication#

OpenSRS uses API keys for authentication. When you connect your OpenSRS account, Pipedream securely stores the keys so you can easily authenticate to OpenSRS APIs in both code and no-code steps.

About OpenSRS#

Reseller Platform for Domains, Email, and SSL

Action#

Accept Completion on Sapling.ai

Description:Have Sapling adapt its system over time. Each suggested completion has a completion UUID. You can pass this information back to Sapling to indicate the completion suggestion was helpful. [See the documentation here](https://sapling.ai/docs/api/autocomplete#accept-completion-post).

Version:0.0.1

Key:sapling_ai-accept-completion

View on GitHub

Sapling.ai Overview#

Sapling.ai offers an AI-driven writing assistant that can help you write better and faster by providing grammar and style suggestions. With its API, you can automate text analysis and correction processes within Pipedream workflows. By integrating Sapling.ai's API in Pipedream, you can create powerful automations that enhance writing quality across various applications, from customer support messages to content creation.

Action Code#

import app from "../../sapling_ai.app.mjs";
import utils from "../../common/utils.mjs";

export default {
  key: "sapling_ai-accept-completion",
  name: "Accept Completion",
  description: "Have Sapling adapt its system over time. Each suggested completion has a completion UUID. You can pass this information back to Sapling to indicate the completion suggestion was helpful. [See the documentation here](https://sapling.ai/docs/api/autocomplete#accept-completion-post).",
  type: "action",
  version: "0.0.1",
  props: {
    app,
    completionId: {
      propDefinition: [
        app,
        "completionId",
      ],
    },
    sessionId: {
      optional: true,
      propDefinition: [
        app,
        "sessionId",
      ],
    },
    query: {
      propDefinition: [
        app,
        "query",
      ],
    },
    completion: {
      type: "string",
      label: "Completion",
      description: "The completion text to accept.",
    },
  },
  methods: {
    acceptCompletion({
      completionId, ...args
    } = {}) {
      return this.app.post({
        path: `/complete/${completionId}/accept`,
        ...args,
      });
    },
  },
  async run({ $: step }) {
    const {
      completionId,
      sessionId: id,
      query,
      completion,
    } = this;

    const sessionId =  utils.generateSessionId(id);

    const response = await this.acceptCompletion({
      step,
      completionId,
      data: {
        session_id: sessionId,
        context: {
          query,
          completion,
        },
      },
    });

    step.export("$summary", `Successfully accepted completion with ID ${completionId}.`);

    return {
      ...response,
      sessionId,
    };
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Sapling.ai	`app`	`app`	This component uses the Sapling.ai app.
Completion ID	`completionId`	`string`	ID of completion or hash returned from a Request Completion.
Session ID	`sessionId`	`string`	Unique name or UUID of document or portion of text that is being checked.
Query	`query`	`string`	Text that should be autocompleted.
Completion	`completion`	`string`	The completion text to accept.

Action Authentication#

Sapling.ai uses API keys for authentication. When you connect your Sapling.ai account, Pipedream securely stores the keys so you can easily authenticate to Sapling.ai APIs in both code and no-code steps.

To retrieve your API Key,

Navigate to your Sapling.AI account and sign in
Go to “User” > “Settings”> “API”

About Sapling.ai #

Language models for enterprise applications.

More Ways to Connect Sapling.ai + OpenSRS#

Other Popular Integrations#

Accept Completion with Sapling.ai API on New DNS Zone Change from OpenSRS API

OpenSRS + Sapling.ai

Try it

Accept Edit with Sapling.ai API on New DNS Zone Change from OpenSRS API

OpenSRS + Sapling.ai

Try it

Reject Edit with Sapling.ai API on New DNS Zone Change from OpenSRS API

OpenSRS + Sapling.ai

Try it

Request Completion with Sapling.ai API on New DNS Zone Change from OpenSRS API

OpenSRS + Sapling.ai

Try it

Request Edits with Sapling.ai API on New DNS Zone Change from OpenSRS API

OpenSRS + Sapling.ai

Try it

Popular Triggers#

New DNS Zone Change from the OpenSRS API

Emit new event when the DNS/ZONE check has passed or failed at the registry. See the documentation

Try it

New Domain Registration from the OpenSRS API

Emit new event for each new domain registration. See the documentation

Try it

New Transfer Status from the OpenSRS API

Emit new event when the status of a domain transfer changes. See the documentation

Try it

Popular Actions#

Initiate Domain Transfer with the OpenSRS API

Initiate a domain transfer to OpenSRS. See the documentation

Try it

Update DNS Records with the OpenSRS API

Update DNS records for a specified domain. See the documentation

Try it

Accept Completion with the Sapling.ai API

Have Sapling adapt its system over time. Each suggested completion has a completion UUID. You can pass this information back to Sapling to indicate the completion suggestion was helpful. See the documentation here

Try it

Accept Edit with the Sapling.ai API

Have Sapling adapt its system over time. Each suggested edit has an edit UUID. You can pass this information back to Sapling to indicate the edit suggestion was helpful. See the documentation here

Try it