Cons API Signup: no welcome emails?

Options
JohnPazniokas
JohnPazniokas ✭
Ancient Membership First Reply
in Blackbaud Luminate Online® & Blackbaud TeamRaiser® Discussions

Hello, all.

I've successfully used the Constituent API in .NET to create new user records in the convio system -- I can see the records in the admin console, and the other API calls are successfully returning the appropriate data. All is happy.

My difficulty is that, once the user records are entered, the email address from the profile is not receiving a welcome email. It appears from the "create" call documentation that it SHOULD, by default, but I'm at a loss as to why it's not getting there.

Are there any additional settings that need to be changed in the admin console, or any other potential pitfalls anyone here has come across, that would cause this functionality to fail? It's something that I could theoretically work around, except that the welcome email is the only indication of the user's password. Kind of makes the whole thing moot.

Thanks for any advice...

John

Tagged:

Comments

  • Corey Pudhorodsky
    Corey Pudhorodsky ✭
    Ancient Membership Facilitator 1

    John,

    Can you include what the value of the "no_welcome" parameter is that you're passing to the create server-server method? This may help others reading the post confirm that the proper value is being passed to allow the welcome email to be sent.

  • JohnPazniokas
    JohnPazniokas ✭
    Ancient Membership First Reply
    Corey Pudhorodsky:

    John,

    Can you include what the value of the "no_welcome" parameter is that you're passing to the create server-server method? This may help others reading the post confirm that the proper value is being passed to allow the welcome email to be sent.

    I've tried "f" and "false", and originally was not passing the parameter. None of these values helped.

  • Jeff Mills
    Jeff Mills ✭
    Ancient Membership Facilitator 1

    Are you using the client or server version of the API? If you use the server version and authenticate as an administrator, then no email is sent, which is behavior of the administrative UI.

  • JohnPazniokas
    JohnPazniokas ✭
    Ancient Membership First Reply
    JeffMills :

    Are you using the client or server version of the API? If you use the server version and authenticate as an administrator, then no email is sent, which is behavior of the administrative UI.

    Thanks, Jeff. That's precisely what I'm doing. I need to do this server-side, because we have other work to do on signup -- including hitting our own database -- which requires the server.

    My followup would be: Can I (and how can I) set up a user that will pass authentication and be capable of using the Constituent API, but is not an administrator? The users/groups implementation in Convio is a touch confusing to me.

    Thanks!

  • Jeff Mills
    Jeff Mills ✭
    Ancient Membership Facilitator 1
    JohnPazniokas :

    Thanks, Jeff. That's precisely what I'm doing. I need to do this server-side, because we have other work to do on signup -- including hitting our own database -- which requires the server.

    My followup would be: Can I (and how can I) set up a user that will pass authentication and be capable of using the Constituent API, but is not an administrator? The users/groups implementation in Convio is a touch confusing to me.

    Thanks!

    The login_name and login_password parameters can be used for a non-administrative user. That user can only access their own record in the call, though, meaning that the cons_id and member_id parameters are ignored. I don't think you can use that for sign-up, though, because the record has to already exist before you could authenticate as that user.

  • Sally Heaven
    Sally Heaven ✭
    Ancient Membership Facilitator 2 Name Dropper Photogenic
    JeffMills :

    The login_name and login_password parameters can be used for a non-administrative user. That user can only access their own record in the call, though, meaning that the cons_id and member_id parameters are ignored. I don't think you can use that for sign-up, though, because the record has to already exist before you could authenticate as that user.

    Would it instead be possible to set up in Email a Recurring Delivery that is sent daily to all new API signups (and previous recipients are automatically added to the Do Not Mail group)?

  • Michael
    Michael ✭
    Ancient Membership Facilitator 2
    Sally Heaven:

    Would it instead be possible to set up in Email a Recurring Delivery that is sent daily to all new API signups (and previous recipients are automatically added to the Do Not Mail group)?

    I think it's probably better to do it as Sally mentioned anyway. If they get their welcome email right away, most users probably realize and assume it's just some system thing and ignore it. We send a weekly welcome email to all new members who registered in the previous week, and people actually respond thanking us for noticing they joined... What I mean is, if you're going to do it for some small set of members, you should consider doing if for ALL new joins and in my experience it works better that way anyway.

Categories