TRIGGERcmd
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    IFTTT with Google Calendar: description parameter triggering an error "Action failure message: Illegal characters in parameters"

    General Discussion
    3
    8
    277
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Vander SticheleT
      Thomas Vander Stichele
      last edited by

      Hi,

      I'm trying out an integration where I want to pass the description of a matching calendar event to a local script, so it can parse it for an obsidian URL to open.

      in IFTTT, I ask the applet to just pass the Description as a parameter.

      The activity log shows this error: Action failure message: Illegal characters in parameters

      The description is:

      open obsidian://open?vault=main&file=4%20Archives%2FPKB%2FPeople

      So lots of potential for illegal characters there 😉 Is there a way to ask IFTTT to encode the description in a way that TriggerCMD will accept?

      RussR 1 Reply Last reply Reply Quote 0
      • RussR
        Russ @Thomas Vander Stichele
        last edited by

        @Thomas-Vander-Stichele, you could try checking this checkbox in your user profile:

        8a78162d-b10a-4c73-b721-997e2bc775de-image.png

        Log into your TRIGGERcmd account, then click your name in the upper-right and click Profile to open your profile page.

        Russell VanderMey

        Steve LeeS Thomas Vander SticheleT 2 Replies Last reply Reply Quote 0
        • Steve LeeS
          Steve Lee @Russ
          last edited by

          @Russ is there a good reason this is opt in rather than always the case?

          RussR 1 Reply Last reply Reply Quote 0
          • Thomas Vander SticheleT
            Thomas Vander Stichele @Russ
            last edited by

            @Russ Thank you, that worked! Had no idea that option was there. I couldn't find it in the documentation for IFTTT - might make sense to add it?

            I also had to add double quotes in the IFTTT config around description, otherwise bash would drop everything after & when spawning the command.

            1 Reply Last reply Reply Quote 0
            • RussR
              Russ @Steve Lee
              last edited by

              @Steve-Lee, good question. The reason those characters are blocked by default is for security. If a hacker got ahold of your account and you have those characters enabled, they could use parameters to run arbitrary commands.

              Russell VanderMey

              Steve LeeS 1 Reply Last reply Reply Quote 0
              • Steve LeeS
                Steve Lee @Russ
                last edited by

                @Russ blimey, cross site scripting vulnerability!?

                RussR 1 Reply Last reply Reply Quote 0
                • RussR
                  Russ @Steve Lee
                  last edited by

                  @Steve-Lee, no I mean if you have those characters enabled, you could put a whole command in the parameters field and run a second command, like this:

                  russ@linux:~$ echo hi & echo russ
                  [1] 72
                  russ
                  hi
                  

                  Russell VanderMey

                  Steve LeeS 1 Reply Last reply Reply Quote 0
                  • Steve LeeS
                    Steve Lee @Russ
                    last edited by

                    @Russ yeah, I meant similar to XSS really - untrusted input getting passed and parsed 🙂 And no way to escape. Thanks for explanation.

                    1 Reply Last reply Reply Quote 0
                    • RussR Russ moved this topic from API on
                    • First post
                      Last post