I was wondering if anyone had discovered a better solution to this issue? We were having the same problem described here and thought at first it was linked to naming the metabot Bot in slack wrong (we named it ‘data’), but remaking the Bot and generating a new API key didn’t seem to have any effect.

I went into the database and explicitly added metabot’s permissions in the permissions tables and that solved the issue. Though, I would rather not have to do that every time a new collection is made.