Update DNS Records with OpenSRS API on New Activity Created Event from Strava API

Pipedream makes it easy to connect APIs for OpenSRS, Strava and 2,700+ other apps remarkably fast.

Trigger workflow on

New Activity Created Event from the Strava API

Next, do this

Update DNS Records with the OpenSRS 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 Strava trigger and OpenSRS action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Activity Created Event trigger
1. Connect your Strava account
2. Configure stravaApphook
Configure the Update DNS Records action
1. Connect your OpenSRS account
2. Configure Domain
3. Select a Nameservers OK
4. Configure Number of A Records
5. Configure Number of AAAA Records
6. Configure Number of CNAME Records
7. Configure Number of MX Records
8. Configure Number of TXT Records
9. Optional- Configure JSON Output
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 Activity Created Event on Strava

Description:Emit new event when a new activity is created

Version:0.0.2

Key:strava-activity-created

View on GitHub

Strava Overview#

The Strava API lets you tap into the robust data from Strava's fitness app, which is a playground for athletes worldwide to track their workouts. With Pipedream, you can automate actions based on activities uploaded to Strava, such as running, biking, or swimming. Imagine syncing workout data to spreadsheets for analysis, auto-posting achievements to social media, or integrating with calendar apps for better scheduling. Pipedream's serverless platform makes it a breeze to create workflows that can listen for Strava webhooks, process data, and trigger actions in countless other apps.

Trigger Code#

import strava from "../../strava.app.mjs";

export default {
  key: "strava-activity-created",
  name: "New Activity Created Event",
  description: "Emit new event when a new activity is created",
  version: "0.0.2",
  type: "source",
  props: {
    strava,
    stravaApphook: {
      type: "$.interface.apphook",
      appProp: "strava",
      eventNames: [
        "activity.create",
      ],
    },
  },
  async run(event) {
    console.log(event);
    let details;
    try {
      details = await this.strava.getActivity({
        activityId: event.object_id,
      });
    } catch (err) {
      console.log(`Error fetching activity details: ${err}`);
    }
    let summary = "Activity created";
    if (details && details.name) {
      summary += `: ${details.name}`;
    }
    this.$emit(
      {
        event,
        details,
      },
      {
        summary,
        ts: event.event_time * 1000,
      },
    );
  },
};

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
Strava	`strava`	`app`	This component uses the Strava app.
	`stravaApphook`	`$.interface.apphook`

Trigger Authentication#

Strava uses OAuth authentication. When you connect your Strava account, Pipedream will open a popup window where you can sign into Strava and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Strava API.

Pipedream requests the following authorization scopes when you connect your account:

readactivity:writeactivity:readactivity:read_all

About Strava#

Designed by athletes, for athletes, Strava's mobile app and website connect millions of runners and cyclists through the sports they love.

Action#

Update DNS Records on OpenSRS

Description:Update DNS records for a specified domain. [See the documentation](https://domains.opensrs.guide/docs/set_dns_zone-).

Version:0.0.1

Key:opensrs-update-dns-records

View on GitHub

Action Code#

import app from "../../opensrs.app.mjs";
import utils from "../../common/utils.mjs";
import constants from "../../common/constants.mjs";

export default {
  key: "opensrs-update-dns-records",
  name: "Update DNS Records",
  description: "Update DNS records for a specified domain. [See the documentation](https://domains.opensrs.guide/docs/set_dns_zone-).",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    domain: {
      propDefinition: [
        app,
        "domain",
      ],
    },
    nameserversOk: {
      type: "string",
      label: "Nameservers OK",
      description: "Indicates whether the domain is set up to use the OpenSRS nameservers.",
      default: "0",
      options: [
        {
          label: "Domain is not set up to use the OpenSRS nameservers",
          value: "0",
        },
        {
          label: "Domain is set up to use the OpenSRS nameservers",
          value: "1",
        },
      ],
    },
    numberOfARecords: {
      type: "integer",
      label: "Number of A Records",
      description: "Number of A records to update",
      default: 0,
      reloadProps: true,
    },
    numberOfAAAARecords: {
      type: "integer",
      label: "Number of AAAA Records",
      description: "Number of AAAA records to update",
      default: 0,
      reloadProps: true,
    },
    numberOfCNAMERecords: {
      type: "integer",
      label: "Number of CNAME Records",
      description: "Number of CNAME records to update",
      default: 0,
      reloadProps: true,
    },
    numberOfMXRecords: {
      type: "integer",
      label: "Number of MX Records",
      description: "Number of MX records to update",
      default: 0,
      reloadProps: true,
    },
    numberOfTXTRecords: {
      type: "integer",
      label: "Number of TXT Records",
      description: "Number of TXT records to update",
      default: 0,
      reloadProps: true,
    },
    jsonOutput: {
      type: "boolean",
      label: "JSON Output",
      description: "Whether to output the response in JSON format.",
      optional: true,
      default: true,
    },
  },
  additionalProps() {
    const {
      numberOfARecords,
      numberOfAAAARecords,
      numberOfCNAMERecords,
      numberOfMXRecords,
      numberOfTXTRecords,
      getARecordPropDefinitions,
      getAAAARecordPropDefinitions,
      getCNAMERecordPropDefinitions,
      getMXRecordPropDefinitions,
      getTXTRecordPropDefinitions,
    } = this;

    const aRecords = utils.getAdditionalProps({
      numberOfFields: numberOfARecords,
      fieldName: "a",
      getPropDefinitions: getARecordPropDefinitions,
    });

    const aaaaRecords = utils.getAdditionalProps({
      numberOfFields: numberOfAAAARecords,
      fieldName: "aaaa",
      getPropDefinitions: getAAAARecordPropDefinitions,
    });

    const cnameRecords = utils.getAdditionalProps({
      numberOfFields: numberOfCNAMERecords,
      fieldName: "cname",
      getPropDefinitions: getCNAMERecordPropDefinitions,
    });

    const mxRecords = utils.getAdditionalProps({
      numberOfFields: numberOfMXRecords,
      fieldName: "mx",
      getPropDefinitions: getMXRecordPropDefinitions,
    });

    const txtRecords = utils.getAdditionalProps({
      numberOfFields: numberOfTXTRecords,
      fieldName: "txt",
      getPropDefinitions: getTXTRecordPropDefinitions,
    });

    return Object.assign({}, aRecords, aaaaRecords, cnameRecords, mxRecords, txtRecords);
  },
  methods: {
    getARecordPropDefinitions({
      prefix, label,
    } = {}) {
      return {
        [`${prefix}ipAddress`]: {
          type: "string",
          label: `${label} - IP Address`,
          description: "The IPv4 address for the A record. A numeric address that computers recognize eg. `123.45.54.123`.",
        },
        [`${prefix}subdomain`]: {
          type: "string",
          label: `${label} - Subdomain`,
          description: "The subdomain for the A record. The third level of the domain name, such as `www` or `ftp`.",
          optional: true,
        },
      };
    },
    getAAAARecordPropDefinitions({
      prefix, label,
    } = {}) {
      return {
        [`${prefix}ipv6Address`]: {
          type: "string",
          label: `${label} - IPv6 Address`,
          description: "The IPv6 address for the AAAA record. A numeric address that computers recognize eg. `2001:0db8:85a3:0000:0000:8a2e:0370:7334`.",
        },
        [`${prefix}subdomain`]: {
          type: "string",
          label: `${label} - Subdomain`,
          description: "The subdomain for the AAAA record. The third level of the domain name, such as `www` or `ftp`.",
        },
      };
    },
    getCNAMERecordPropDefinitions({
      prefix, label,
    } = {}) {
      return {
        [`${prefix}hostname`]: {
          type: "string",
          label: `${label} - Hostname`,
          description: "The FQDN of the domain that you want to access.",
        },
        [`${prefix}subdomain`]: {
          type: "string",
          label: `${label} - Subdomain`,
          description: "The third level of the domain name, such as `www` or `ftp`.",
        },
      };
    },
    getMXRecordPropDefinitions({
      prefix, label,
    } = {}) {
      return {
        [`${prefix}priority`]: {
          type: "string",
          label: `${label} - Priority`,
          description: "The priority of the target host, lower value means more preferred.",
          optional: true,
        },
        [`${prefix}hostname`]: {
          type: "string",
          label: `${label} - Hostname`,
          description: "The FQDN of the domain that you want to access.",
        },
        [`${prefix}subdomain`]: {
          type: "string",
          label: `${label} - Subdomain`,
          description: "The third level of the domain name, such as `www` or `ftp`.",
        },
      };
    },
    getTXTRecordPropDefinitions({
      prefix, label,
    } = {}) {
      return {
        [`${prefix}subdomain`]: {
          type: "string",
          label: `${label} - Subdomain`,
          description: "The third level of the domain name, such as `www` or `ftp`.",
        },
        [`${prefix}text`]: {
          type: "string",
          label: `${label} - Text`,
          description: "The text content for the TXT record.",
        },
      };
    },
    aRecordPropsMapper(prefix) {
      const {
        [`${prefix}ipAddress`]: ipAddress,
        [`${prefix}subdomain`]: subdomain,
      } = this;
      return {
        dt_assoc: {
          item: [
            ...utils.addItem("subdomain", subdomain),
            ...utils.addItem("ip_address", ipAddress),
          ],
        },
      };
    },
    aaaaRecordPropsMapper(prefix) {
      const {
        [`${prefix}ipv6Address`]: ipv6Address,
        [`${prefix}subdomain`]: subdomain,
      } = this;
      return {
        dt_assoc: {
          item: [
            ...utils.addItem("subdomain", subdomain),
            ...utils.addItem("ipv6_address", ipv6Address),
          ],
        },
      };
    },
    cnameRecordPropsMapper(prefix) {
      const {
        [`${prefix}hostname`]: hostname,
        [`${prefix}subdomain`]: subdomain,
      } = this;
      return {
        dt_assoc: {
          item: [
            ...utils.addItem("subdomain", subdomain),
            ...utils.addItem("hostname", hostname),
          ],
        },
      };
    },
    mxRecordPropsMapper(prefix) {
      const {
        [`${prefix}priority`]: priority,
        [`${prefix}hostname`]: hostname,
        [`${prefix}subdomain`]: subdomain,
      } = this;
      return {
        dt_assoc: {
          item: [
            ...utils.addItem("subdomain", subdomain),
            ...utils.addItem("hostname", hostname),
            ...utils.addItem("priority", priority),
          ],
        },
      };
    },
    txtRecordPropsMapper(prefix) {
      const {
        [`${prefix}subdomain`]: subdomain,
        [`${prefix}text`]: text,
      } = this;
      return {
        dt_assoc: {
          item: [
            ...utils.addItem("subdomain", subdomain),
            ...utils.addItem("text", text),
          ],
        },
      };
    },
    getJsonBody() {
      const {
        domain,
        nameserversOk,
        numberOfARecords,
        numberOfAAAARecords,
        numberOfCNAMERecords,
        numberOfMXRecords,
        numberOfTXTRecords,
        aRecordPropsMapper,
        aaaaRecordPropsMapper,
        cnameRecordPropsMapper,
        mxRecordPropsMapper,
        txtRecordPropsMapper,
      } = this;

      const aRecords = utils.getFieldsProps({
        numberOfFields: numberOfARecords,
        fieldName: "a",
        propsMapper: aRecordPropsMapper,
      });

      const aaaaRecords = utils.getFieldsProps({
        numberOfFields: numberOfAAAARecords,
        fieldName: "aaaa",
        propsMapper: aaaaRecordPropsMapper,
      });

      const cnameRecords = utils.getFieldsProps({
        numberOfFields: numberOfCNAMERecords,
        fieldName: "cname",
        propsMapper: cnameRecordPropsMapper,
      });

      const mxRecords = utils.getFieldsProps({
        numberOfFields: numberOfMXRecords,
        fieldName: "mx",
        propsMapper: mxRecordPropsMapper,
      });

      const txtRecords = utils.getFieldsProps({
        numberOfFields: numberOfTXTRecords,
        fieldName: "txt",
        propsMapper: txtRecordPropsMapper,
      });

      const records = [
        ...aRecords,
        ...aaaaRecords,
        ...cnameRecords,
        ...mxRecords,
        ...txtRecords,
      ];

      return {
        data_block: {
          dt_assoc: {
            item: [
              ...utils.addItem("protocol", constants.PROTOCOL.XCP),
              ...utils.addItem("object", constants.OBJECT_TYPE.DOMAIN),
              ...utils.addItem("action", constants.ACTION_TYPE.SET_DNS_ZONE),
              {
                "@_key": "attributes",
                "dt_assoc": {
                  item: [
                    ...utils.addItem("domain", domain),
                    ...(records.length
                      ? [
                        ...utils.addItem("nameservers_ok", nameserversOk),
                        {
                          "@_key": "records",
                          "dt_assoc": {
                            item: [
                              ...utils.addDnsRecord("A", aRecords),
                              ...utils.addDnsRecord("AAAA", aaaaRecords),
                              ...utils.addDnsRecord("CNAME", cnameRecords),
                              ...utils.addDnsRecord("MX", mxRecords),
                              ...utils.addDnsRecord("TXT", txtRecords),
                            ],
                          },
                        },
                      ]
                      : []
                    ),
                  ],
                },
              },
            ],
          },
        },
      };
    },
    updateDnsRecords(args) {
      return this.app.post(args);
    },
  },
  async run({ $ }) {
    const {
      updateDnsRecords,
      getJsonBody,
      jsonOutput,
    } = this;

    const response = await updateDnsRecords({
      $,
      jsonBody: getJsonBody(),
      jsonOutput,
    });

    $.export("$summary", "Successfully updated DNS records.");
    return response;
  },
};

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
OpenSRS	`app`	`app`	This component uses the OpenSRS app.
Domain	`domain`	`string`	The domain name to register, update, or transfer.
Nameservers OK	`nameserversOk`	`string`	Select a value from the drop down menu:`{ "label": "Domain is not set up to use the OpenSRS nameservers", "value": "0" }{ "label": "Domain is set up to use the OpenSRS nameservers", "value": "1" }`
Number of A Records	`numberOfARecords`	`integer`	Number of A records to update
Number of AAAA Records	`numberOfAAAARecords`	`integer`	Number of AAAA records to update
Number of CNAME Records	`numberOfCNAMERecords`	`integer`	Number of CNAME records to update
Number of MX Records	`numberOfMXRecords`	`integer`	Number of MX records to update
Number of TXT Records	`numberOfTXTRecords`	`integer`	Number of TXT records to update
JSON Output	`jsonOutput`	`boolean`	Whether to output the response in JSON format.

Update DNS Records with OpenSRS API on New Activity Created Event from Strava API

Pipedream makes it easy to connect APIs for OpenSRS, Strava and 2,700+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,700+apps by most popular

1
-
24
of
2,700+
apps by most popular