Add BBPS transaction ID as a custom field on the gift

Options

Hi everyone, I'm hoping someone can help me out with a power automate flow. We have just gone live with BBMS and I'm trying to add the BBPS transaction ID onto the gift as a custom field. I've connected the payments API and can see the endpoint I want in power automate, but although the custom fields are being added, the value is null. I'm stumped as to how to fix it, and I'm not getting much information from the power automate response. Can anyone make any suggestions?

I'm in Australia and just about to log off for the day so if I don't respond to comments immediately it's just because I'm sleeping :)

Comments

  • @Jenny Mulcock - Did you create a custom connector for the Payments API to Power Automate?

  • @Heather McLean yep, so in theory it should be working. Someone has told me now though that BB haven't made the Payments API available in power automate due to security/PCI concerns (although you can see the fields there and they look available).

  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 PowerUp Challenge #3 Gift Management Name Dropper

    @Jenny Mulcock
    you will need to provide more information on your flow as to what you are doing. which api endpoint are you calling, how you call it, and the “output” from the call.

  • Hi Alex :). It's a very simple flow at the moment. I'm starting with a gifts list. For each gift in the list, it calls the Payments BBPS Transaction ID endpoint and the action is to add a gift custom field, using the transaction ID as the value.

    I've spoken to BB support and they've said that the payments API is not available in power automate for security/PCI reasons, so it seems that's why I can't access the transaction ID. Someone did suggest that I try to access it via an HTTP call, but I'm not sure how to do that!
  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 PowerUp Challenge #3 Gift Management Name Dropper

    @Jenny Mulcock
    A few point of clarity:

    eca4d942b0712db83b3af599f7adb4f5-huge-im
    • Once you are able to issue the Payment API, then the world is your oyster, go have fun adding any gift custom fields you like from info retrieved by the payment data in BBMS.
  • @Alex Wong thank you, I'll have a read. ?

  • Glen Hutson
    Glen Hutson Blackbaud Employee
    Tenth Anniversary Kudos 3 Name Dropper Participant

    @Jenny Mulcock / @Alex Wong

    At last check, the Send an HTTP Request action was not allowed to touch the Payments Endpoints. I can do some double-checking to see if that policy changed, but thought to go ahead and mention that to save some time.

    Update: Confirmed that the Send an HTTP Request is not setup to access the Payments APIs. If you create a custom connector, that should work.

  • @Glen Hutson thanks for letting me know. Foiled again!

  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 PowerUp Challenge #3 Gift Management Name Dropper

    @Glen Hutson
    Hmm, didn't think it was explicitly blocked. However, I'm sure I have make the endpoint call before, probably through the normal HTTP action then.

Categories